How severe is CVE-2026-32274?

No CVSS score has been assigned to CVE-2026-32274 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-32274?

CVE-2026-32274 affects the following packages: black (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-32274?

Update black to 26.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32274 is resolved across your whole dependency graph.

How do I detect CVE-2026-32274 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for black, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-32274 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-32274 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-32274 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-32274?

CVE-2026-32274 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 51th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-32274?

CVE-2026-32274 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-32274 published, and has it been updated?

CVE-2026-32274 was published on March 12, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-32274 — black

Fix: psf/black@4937fe6

CVE-2026-32274 is a Path Traversal vulnerability in black. A fix is available for black — see the affected versions and patch details below.

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

Also known asGHSA-3936-cmfr-pm3mPYSEC-2026-2121

Published

Mar 12, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32274.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍black

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.

Patches

Fixed in Black 26.3.1.

Workarounds

Do not allow untrusted user input into the value of the --python-cell-magics option.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`black`	≥ 24.3.0&&< 26.3.1	26.3.1`pip install --upgrade 'black==26.3.1'`

Affected Products

1 product · 1 configurations

Application

blackpython

< 26.3.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for black, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update black to 26.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32274 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2026-32274 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.5	`ansible-automation-platform-25/hub-rhel8:1777393635`	RHSA-2026:13553
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/ansible-dev-tools-rhel9:1777390240`	RHSA-2026:13545
Red Hat OpenShift AI 2.25	`rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9:1776319193`	RHSA-2026:10184
Red Hat OpenShift AI 3.3	`rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9:1790331087`	RHSA-2026:73987

Frequently Asked Questions

### Impact 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. ### Patches Fixed in Black 26.3.1. ### Workarounds Do not allow untrusted user input into the value of the `--python-cell-magics` option.

O3 Security · Impact-Aware SCA

Is CVE-2026-32274 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works