Is black 26.3 vulnerable?

PyPI · 2 releases from 26.3.0 to 26.3.1 · latest black is 26.10.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. black 26.3.1, the last 26.3 release, is affected by 1 known security advisory (1 high), including CVE-2026-114134. 1 more affects earlier 26.3.x releases. Upgrade to 26.10.1 or later to fix all of them.

Upgrade with:pip install 'black>=26.10.1'

Is your project on an affected black?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting black 26.3.1

  • HighCVE-2026-114134GHSA-cg8m-r9f2-5wm222 Oct 2026

    Black: GitHub Action installs unvalidated required-version from pyproject.toml

    Affected
    <26.10.1
    Fixed in
    26.10.1

Fixed within 26.3.x, affecting earlier releases

  • HighCVE-2026-32274GHSA-3936-cmfr-pm3m12 Mar 2026

    Black: Arbitrary file writes from unsanitized user input in cache file name

    Affected
    >=24.3.0 <26.3.1
    Fixed in
    26.3.1

Every black 26.3.x release

Affected: 26.3.0 to 26.3.1. Latest black: 26.10.1.

VersionKnown advisories
black 26.3.1CVE-2026-114134
black 26.3.0CVE-2026-114134, CVE-2026-32274

Which of your client projects are still on black 26.3?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact black version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other black versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.