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 53% 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: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Black is the uncompromising Python code formatter. Starting in version 24.3.0 and prior to version 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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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%
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

Published

March 12, 2026

Last Modified

August 3, 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(5)

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 / EcosystemFix (by version range) / 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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
black20.8b1-4 ... 26.3.1-1 (44 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
black23.1.0-1 ... 26.5.1-2 (31 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
black25.1.0-3
  • every version up to 25.1.0-3+deb13u1: fixed in 25.1.0-3+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
black25.1.0-3 ... 26.1.0-1 (6 versions)
  • every version up to 26.3.1-1: fixed in 26.3.1-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
black18.3a0 ... 26.3.0 (70 versions)
  • 24.3.0 up to 26.3.1: fixed in 26.3.1
  • every version up to 26.3.1: fixed in 26.3.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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.

Showing the most recent 100 of 135 total refreshes for this CVE.

  1. 2026-10-05 17:42 UTCEPSS rescore
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-01 19:49 UTCEPSS rescore
  5. 2026-09-30 15:03 UTCEPSS rescore
  6. 2026-09-28 13:51 UTCEPSS rescore
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-26 15:58 UTCEPSS rescore
  9. 2026-09-26 00:26 UTCEPSS rescore
  10. 2026-09-21 23:46 UTCOSV refresh
  11. 2026-09-20 20:15 UTCEPSS rescore
  12. 2026-09-20 20:15 UTCEPSS rescore
  13. 2026-09-18 19:28 UTCEPSS rescore
  14. 2026-09-18 19:27 UTCEPSS rescore
  15. 2026-09-17 19:30 UTCEPSS rescore
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-13 16:47 UTCEPSS rescore
  19. 2026-09-12 15:01 UTCEPSS rescore
  20. 2026-09-11 14:52 UTCEPSS rescore
  21. 2026-09-10 09:34 UTCEPSS rescore
  22. 2026-09-08 22:00 UTCEPSS rescore
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 19:10 UTCOSV refresh
  3. 2026-09-02 14:11 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-09-01 04:39 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-24 14:17 UTCEPSS rescore
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 11:41 UTCEG score recompute
  23. 2026-08-16 11:41 UTCVendor advisory
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 20:21 UTCVendor advisory
  27. 2026-08-14 07:42 UTCEG score recompute
  28. 2026-08-14 07:42 UTCVendor advisory
  29. 2026-08-13 22:00 UTCEPSS rescore
  30. 2026-08-12 22:43 UTCEG score recompute
  31. 2026-08-12 22:43 UTCVendor advisory
  32. 2026-08-12 13:50 UTCEPSS rescore
  33. 2026-08-11 21:42 UTCEG score recompute
  34. 2026-08-11 21:42 UTCVendor advisory
  35. 2026-08-11 04:50 UTCEG score recompute
  36. 2026-08-11 04:50 UTCVendor advisory
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-10 08:38 UTCVendor advisory
  39. 2026-08-09 20:00 UTCEG score recompute
  40. 2026-08-09 20:00 UTCVendor advisory
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-09 07:22 UTCEG score recompute
  43. 2026-08-09 07:22 UTCVendor advisory
  44. 2026-08-08 16:37 UTCEPSS rescore
  45. 2026-08-08 06:41 UTCVendor advisory
  46. 2026-08-07 18:03 UTCEG score recompute
  47. 2026-08-07 18:03 UTCVendor advisory
  48. 2026-08-06 19:48 UTCEG score recompute
  49. 2026-08-06 19:48 UTCVendor advisory
  50. 2026-08-06 13:46 UTCEPSS rescore
  51. 2026-08-06 01:55 UTCEG score recompute
  52. 2026-08-06 01:55 UTCVendor advisory
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 10:38 UTCEPSS rescore
  56. 2026-08-03 21:21 UTCVendor advisory
  57. 2026-08-03 20:43 UTCEG score recompute
  58. 2026-08-03 20:43 UTCVendor advisory
  59. 2026-08-03 10:36 UTCEPSS rescore
  60. 2026-08-02 17:19 UTCEG score recompute
  61. 2026-08-02 17:19 UTCVendor advisory
  62. 2026-08-02 02:27 UTCEPSS rescore
  63. 2026-08-01 04:16 UTCEPSS rescore
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-25 14:18 UTCEPSS rescore
  69. 2026-07-25 14:17 UTCEPSS rescore
  70. 2026-07-24 14:17 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 03:08 UTCEG score recompute
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-22 14:08 UTCEPSS rescore

Related CVEs(same product + 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. Starting in version 24.3.0 and prior to version 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…
When was CVE-2026-32274 disclosed?
CVE-2026-32274 was first published on March 12, 2026, with the most recent update on August 3, 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 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-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?
A fix for CVE-2026-32274 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32274 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs