CVE-2026-32274

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 56% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Black is the uncompromising Python code formatter. Prior to 26.3.1, Black writes a cache file, the name of which is computed from various formatting options. The value of the --python-cell-magics option was placed in the filename without sanitization, which allowed an attacker who controls the value of this argument to write cache files to arbitrary file system locations. Fixed in Black 26.3.1.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

March 12, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 3, 2026
Patch available. Sources: github_commit, github_pr, github_release, github, redhat.
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-32274.json
redhat

2447111 – (CVE-2026-32274) CVE-2026-32274 black: Black: Arbitrary file writes from unsanitized user input in cache file name

https://bugzilla.redhat.com/show_bug.cgi?id=2447111
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-32274
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13553
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13545
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10184
github Patch Available

Arbitrary file writes from unsanitized user input in cache file name · Advisory · psf/black · GitHub

https://github.com/psf/black/security/advisories/GHSA-3936-cmfr-pm3m
github_release Patch Available

26.3.1

Patch available: psf/black 26.3.1

https://github.com/psf/black/releases/tag/26.3.1
github_pr

Fix some shenanigans with the cache file and IPython

Fix merged in psf/black PR #5038 on 2026-03-12 — awaiting tagged release

https://github.com/psf/black/pull/5038
github_commit

commit 4937fe6cf241 (psf/black)

Fix landed in psf/black commit 4937fe6cf241 — awaiting tagged release

https://github.com/psf/black/commit/4937fe6cf241139ddbfc16b0bdbb5b422798909d

Vendor Advisories for CVE-2026-32274(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform-25/lightspeed-rhel8:17774038722026-05-04redhat
redhatansible-automation-platform-26/platform-resource-runner-rhel9:17773903332026-05-04redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17763192752026-04-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
black18.3a0 ... 26.3.0 (70 versions)26.3.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-25 14:18 UTCEPSS rescore
  4. 2026-07-25 14:17 UTCEPSS rescore
  5. 2026-07-24 14:17 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:08 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-21 15:24 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 02:29 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-18 06:59 UTCOSV refresh
  21. 2026-07-16 17:03 UTCEPSS rescore
  22. 2026-07-16 17:03 UTCEPSS rescore
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 20 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 04:34 UTCEG score recompute
  19. 2026-06-30 04:34 UTCVendor advisory
  20. 2026-06-30 04:31 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32274?
CVE-2026-32274 is a high vulnerability published on March 12, 2026. Black is the uncompromising Python code formatter. Prior to 26.3.1, Black writes a cache file, the name of which is computed from various formatting options. The value of the --python-cell-magics option was placed in the filename without sanitization, which allowed an attacker who controls the…
When was CVE-2026-32274 disclosed?
CVE-2026-32274 was first published in the National Vulnerability Database on March 12, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32274 actively exploited?
CVE-2026-32274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.9% of all scored CVEs.
What is the CVSS score of CVE-2026-32274?
CVE-2026-32274 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32274, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32274

Explore →

Is Your Infrastructure Affected by CVE-2026-32274?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs