CVE and update status of the FreeBSD ports tree3,639 unaddressed CVEs in 721 portsAll times are CET
CVE details

CVE-2026-114134

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.

Score
8.7 high
Published
2026-11-05
Links
NVD · cve.org · Report wrong data

Matched ports (1)

PortPackageVersionStatusMaintainer
devel/py-blackpy312-black26.5.1unaddressedsunpoet@FreeBSD.org

Template for a VuXML entry

Check the content

Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.

Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>py312-black -- FIXME</topic>
    <affects>
      <package>
	<name>py312-black</name>
	<range><lt>26.10.1</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>CVE-2026-114134: 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.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-114134</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-114134</url>
    </references>
    <dates>
      <discovery>2026-11-05</discovery>
      <entry>2026-11-06</entry>
    </dates>
  </vuln>