CVE-2026-112900

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.3% (70th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — Patch released this weekElevated

Also known asEUVD-2026-104661 (ENISA EUVD) · GHSA-w889-685w-c8fh (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Pillow is a Python imaging library. From 2.6.0 until 13.0.0, Pillow is vulnerable to argument injection when invoking Ghostscript for EPS input. EpsImagePlugin.Ghostscript passes a caller-controlled input filename after -f without converting it to a safe absolute path, so a name beginning with a hyphen can be interpreted as a Ghostscript option. An attacker who controls the filename can inject Ghostscript arguments. Arbitrary command execution specifically requires a leading @ argument-file filename and control of the referenced text file containing additional Ghostscript arguments; the reported chain reproduces with the default -dSAFER invocation. This issue is fixed in version 13.0.0.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.3%
EPSS %ILE
70th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.3% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 19, 2026

Last Modified

October 27, 2026

Advisory Details (3)

Auto-updated Nov 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Argument Injection in Ghostscript call, potentially leading into RCE · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-w889-685w-c8fh
GitHub release Patch Available

13.0.0

Patch available: python-pillow/Pillow 13.0.0

https://github.com/python-pillow/Pillow/releases/tag/13.0.0
GitHub commit Patch Available

commit a2c363141da3 (python-pillow/Pillow)

Patch available: python-pillow/Pillow 13.0.0 (contains commit a2c363141da3)

https://github.com/python-pillow/Pillow/commit/a2c363141da31a265dd536c945677db4b64f3ec9

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-pillow-0:5.1.1-15.el8_4.32026-11-11redhat
redhatpython-pillow-0:5.1.1-20.el8_6.22026-11-11redhat
redhatpython-pillow-0:5.1.1-20.el8_8.22026-11-11redhat
redhatrhaii/vllm-rocm-rhel9:17934444562026-11-03redhat
redhatrhaii/model-opt-cuda-rhel9:17934443392026-11-03redhat
redhatrhaii/vllm-spyre-rhel9:17934444092026-11-03redhat
redhatrhaii/vllm-gaudi-rhel9:17934445102026-11-03redhat
redhatrhaii/vllm-cuda-rhel9:17934446002026-11-03redhat
redhatrhaii/vllm-cpu-rhel9:17934445542026-11-03redhat
redhatpython-pillow-0:5.1.1-36.el8_102026-10-30redhat
pipPillow @ 13.0.0 (fixes >= 2.6.0, < 13.0.0)—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
pillow10.0.0-1 ... 9.5.0-1 (24 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 13.0.0-1 (14 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pillow11.1.0-5 ... 13.0.0-1 (10 versions)
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pillow10.0.0 ... 9.5.0 (78 versions)
  • 2.6.0 up to 13.0.0: fixed in 13.0.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 56× 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 v3 → 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-13 01:21 UTCEchelonGraph re-scored
  2. 2026-11-13 01:21 UTCVendor advisory
  3. 2026-11-13 01:21 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  5. 2026-11-12 02:00 UTCEchelonGraph re-scored
  6. 2026-11-12 02:00 UTCVendor advisory
  7. 2026-11-12 02:00 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  8. 2026-11-11 16:38 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  9. 2026-11-11 02:39 UTCEchelonGraph re-scored
  10. 2026-11-11 02:39 UTCVendor advisory
  11. 2026-11-11 02:38 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  12. 2026-11-10 16:42 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  13. 2026-11-10 13:14 UTCEchelonGraph re-scored
  14. 2026-11-10 13:14 UTCVendor advisory
  15. 2026-11-10 13:14 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  16. 2026-11-09 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  17. 2026-11-09 13:50 UTCEchelonGraph re-scored
  18. 2026-11-09 13:50 UTCVendor advisory
  19. 2026-11-09 13:50 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  20. 2026-11-08 16:38 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  21. 2026-11-08 14:29 UTCEchelonGraph re-scored
  22. 2026-11-08 14:29 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  23. 2026-11-07 16:38 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  24. 2026-11-07 15:08 UTCEchelonGraph re-scored
  25. 2026-11-07 15:08 UTCVendor advisory
Show 62 more
  1. 2026-11-07 15:08 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  2. 2026-11-06 16:36 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  3. 2026-11-06 15:47 UTCEchelonGraph re-scored
  4. 2026-11-06 15:47 UTCVendor advisory
  5. 2026-11-06 15:47 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  6. 2026-11-05 23:25 UTCOSV refresh
  7. 2026-11-05 16:36 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  8. 2026-11-05 16:26 UTCEchelonGraph re-scored
  9. 2026-11-05 16:26 UTCVendor advisory
  10. 2026-11-05 16:26 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  11. 2026-11-04 17:45 UTCEchelonGraph re-scored
  12. 2026-11-04 17:45 UTCVendor advisory
  13. 2026-11-04 17:45 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  14. 2026-11-04 16:34 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  15. 2026-11-03 18:23 UTCEchelonGraph re-scored
  16. 2026-11-03 18:23 UTCVendor advisory
  17. 2026-11-03 18:23 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  18. 2026-11-03 16:46 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  19. 2026-11-03 11:16 UTCEchelonGraph re-scored
  20. 2026-11-03 11:16 UTCVendor advisory
  21. 2026-11-03 11:16 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  22. 2026-11-02 16:44 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  23. 2026-11-02 11:55 UTCEchelonGraph re-scored
  24. 2026-11-02 11:55 UTCVendor advisory
  25. 2026-11-02 11:55 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  26. 2026-11-01 16:33 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  27. 2026-11-01 12:34 UTCVendor advisory
  28. 2026-11-01 12:34 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  29. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-w889-685w-c8fh · GitHub severity CRITICAL
  30. 2026-11-01 07:59 UTCEchelonGraph re-scored
  31. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  32. 2026-10-31 13:12 UTCEchelonGraph re-scored
  33. 2026-10-31 13:12 UTCVendor advisory
  34. 2026-10-30 16:33 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  35. 2026-10-30 13:46 UTCEchelonGraph re-scored
  36. 2026-10-29 16:32 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  37. 2026-10-29 14:16 UTCEchelonGraph re-scored
  38. 2026-10-28 16:31 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  39. 2026-10-28 14:55 UTCEchelonGraph re-scored
  40. 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  41. 2026-10-27 15:09 UTCEchelonGraph re-scored▲ 0.60
  42. 2026-10-27 15:06 UTCNVD updateCVSS v3 → 9.8
  43. 2026-10-26 16:32 UTCEchelonGraph re-scored
  44. 2026-10-26 16:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  45. 2026-10-25 16:57 UTCEchelonGraph re-scored
  46. 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  47. 2026-10-25 14:51 UTCEchelonGraph re-scored
  48. 2026-10-24 17:36 UTCEchelonGraph re-scored
  49. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  50. 2026-10-23 18:15 UTCEchelonGraph re-scored
  51. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  52. 2026-10-22 18:51 UTCEchelonGraph re-scored
  53. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  54. 2026-10-21 19:29 UTCEchelonGraph re-scored
  55. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  56. 2026-10-20 20:06 UTCEchelonGraph re-scored
  57. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  58. 2026-10-20 15:26 UTCEchelonGraph re-scored
  59. 2026-10-20 14:47 UTCEchelonGraph re-scored
  60. 2026-10-19 22:28 UTCEchelonGraph re-scored
  61. 2026-10-19 22:15 UTCEchelonGraph re-scoredFirst assessed: 9.2 CRITICAL
  62. 2026-10-19 22:12 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCkavin-jindal/CVE-2026-112900-PoC
    Published Oct 25, 2026

    Proof of Concept (PoC) demonstrating Argument Injection in Pillow's Ghostscript call (Pillow < 13.0.0) potentially leading to arbitrary command execution (RCE).

    Open source ↗

Frequently asked(5)

What is CVE-2026-112900?
CVE-2026-112900 is a critical-severity vulnerability; its CVE record was published on October 19, 2026. Pillow is a Python imaging library. From 2.6.0 until 13.0.0, Pillow is vulnerable to argument injection when invoking Ghostscript for EPS input. EpsImagePlugin.Ghostscript passes a caller-controlled input filename after -f without converting it to a safe absolute path, so a name beginning with a…
When was the CVE record for CVE-2026-112900 published?
The CVE record for CVE-2026-112900 was published on October 19, 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 October 27, 2026; the record at its source may have been updated since.
Is CVE-2026-112900 actively exploited?
CVE-2026-112900 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112900?
CVE-2026-112900 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-112900?
A fix for CVE-2026-112900 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112900 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-112900

Explore →

Is Your Infrastructure Affected by CVE-2026-112900?

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