CVE-2026-114134

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-117785 (ENISA EUVD) · GHSA-cg8m-r9f2-5wm2 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 22, 2026

Last Modified

November 12, 2026

Advisory Details (3)

Auto-updated Nov 5, 2026
Patch available. Sources: github, github_commit, github_pr.
GitHub commit

commit ac1f71563aec (psf/black)

Fix landed in psf/black commit ac1f71563aec — awaiting tagged release

https://github.com/psf/black/commit/ac1f71563aeccf73cf13ece00f231d9d6c66a514
GitHub pull request

Action: validate required-version better

Fix merged in psf/black PR #5510 on 2026-10-10 — awaiting tagged release

https://github.com/psf/black/pull/5510
GitHub advisoryMentions a patch (unverified)

GitHub Action installs unvalidated required-version from pyproject.toml · Advisory · psf/black · GitHub

https://github.com/psf/black/security/advisories/GHSA-cg8m-r9f2-5wm2

Vendor Advisories for CVE-2026-114134(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipblack @ 26.10.1 (fixes < 26.10.1)—ghsa

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
black23.1.0-1 ... 26.5.1-2 (34 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
black25.1.0-3 ... 26.5.1-2 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
black25.1.0-3 ... 26.5.1-2 (11 versions)
  • every version up to 26.10.1-1: fixed in 26.10.1-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
black18.3a0 ... 26.5.1 (74 versions)
  • every version up to 26.10.1: fixed in 26.10.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 15× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 22:29 UTCEchelonGraph re-scored
  2. 2026-11-12 22:29 UTCGHSA enrichmentGHSA-cg8m-r9f2-5wm2 · GitHub severity HIGH
  3. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-11-11 03:36 UTCEchelonGraph re-scored
  6. 2026-11-11 03:36 UTCGHSA enrichmentGHSA-cg8m-r9f2-5wm2 · GitHub severity HIGH
  7. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-11-09 18:27 UTCEchelonGraph re-scored
  9. 2026-11-09 18:27 UTCGHSA enrichmentGHSA-cg8m-r9f2-5wm2 · GitHub severity HIGH
  10. 2026-11-09 17:45 UTCEchelonGraph re-scored
  11. 2026-11-09 17:45 UTCGHSA enrichmentGHSA-cg8m-r9f2-5wm2 · GitHub severity HIGH
  12. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-11-05 21:28 UTCEchelonGraph re-scored
  17. 2026-11-05 21:28 UTCGHSA enrichmentGHSA-cg8m-r9f2-5wm2 · GitHub severity HIGH
  18. 2026-11-05 20:27 UTCMITRE cvelistV5CVSS → 8.7 · CVSS v4 → 8.7
  19. 2026-11-05 20:27 UTCEchelonGraph re-scoredFirst assessed: 8.7 HIGH
  20. 2026-11-05 20:27 UTCGHSA enrichmentGHSA-cg8m-r9f2-5wm2 · GitHub severity HIGH
  21. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-cg8m-r9f2-5wm2 · GitHub severity HIGH
  22. 2026-10-25 14:50 UTCEchelonGraph re-scored
  23. 2026-10-22 16:21 UTCEchelonGraph re-scored

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-114134?
CVE-2026-114134 is a high-severity vulnerability; its CVE record was published on October 22, 2026. 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…
When was the CVE record for CVE-2026-114134 published?
The CVE record for CVE-2026-114134 was published on October 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-114134 actively exploited?
CVE-2026-114134 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114134?
CVE-2026-114134 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114134?
A fix for CVE-2026-114134 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-114134 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-114134

Explore →

Is Your Infrastructure Affected by CVE-2026-114134?

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

Book a Demo →Browse All CVEs