Live › vulnerability › CVE-2026-114134
Go to dashboardThe Black GitHub Action reads the version to install from tool.black.required-version in pyproject.toml when use_pyproject is true, and does not validate it. A pull request that points that value at an attacker-controlled package source can run arbitrary code in the context of the victim's CI run and repository.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| black | pypi | < 26.10.1 | 26.10.1 |
s workflow files for psf/black or uses: psf/black' with use_pyproject: true26.10.1, fixed in 26.10.1)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The GitHub Action bundled with Black can read the version from tool.black.required-version if use_pyproject is set to True. This version is not validated and therefore can be used to execute untrusted code in the context of a victim's repository.
This is similar to the previous CVE-2026-31900. The value in tool.black.required-version is accepted as the version to be installed by the action without validation.
Reproduction requires a victim to use Black's GitHub Action with use_pyproject: true. The attacker would then issue a PR to the victim's repository with pyproject.toml edited so that Black points to a malicious repository.
This is a remote code execution vulnerability impacting users using the GitHub Action bundled with psf/black and using the use_pyproject: true setting.
This page as .md · .json · in your agent: get_signal("CVE-2026-114134")
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.