Inclusion of Functionality from Untrusted Control Sphere Affecting nemo package, versions <2.7.3-r39


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.4% (35th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-NEMO-21693141
  • published24 Oct 2026
  • disclosed5 Nov 2026

Introduced: 24 Oct 2026

NewCVE-2026-114134  (opens in a new tab)
CWE-829  (opens in a new tab)

How to fix?

Upgrade Chainguard nemo to version 2.7.3-r39 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nemo package and not the nemo package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Black is the uncompromising Python code formatter. Prior to 26.10.1, the Black GitHub Action with use_pyproject: true accepts tool.black.required-version from pyproject.toml without validating that it is a released Black version specifier. An attacker who can submit a pull request can change that field to a direct reference to attacker-controlled code, causing the workflow to install and execute the code in the victim repository's GitHub Actions context. This issue is fixed in version 26.10.1.