CVE-2026-96637

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st 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

Also known asEUVD-2026-107569 (ENISA EUVD) · GHSA-g842-9rc4-69pw (GitHub Security Advisories) · PYSEC-2026-4338 (OSV.dev)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Pillow is a Python imaging library. Prior to 13.0.0, SpiderImageFile.seek() in src/PIL/SpiderImagePlugin.py reparses a later SPIDER stack frame and replaces self._size without rerunning Image._decompression_bomb_check(). A tiny file can use a safe first frame to pass Image.open() and then declare very large dimensions in a later mode F frame. Loading that frame allocates approximately four bytes per attacker-declared pixel and can consume multiple gigabytes of memory. This issue is fixed in version 13.0.0.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
44
EG Risk 44/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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.
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 partial (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
0.4%
EPSS %ILE
31st
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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: 14 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 partial (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; 60 days if it is not.

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

Last Modified

October 27, 2026

Advisory Details (4)

Auto-updated Oct 21, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Decompression bomb check bypass in SpiderImagePlugin.seek() leads to unbounded allocation DoS · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-g842-9rc4-69pw
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 pull request Patch Available

Add decompression bomb check after SPIDER seek

Patch available: python-pillow/Pillow 13.0.0 (PR #10076 merged 2026-09-29)

https://github.com/python-pillow/Pillow/pull/10076
GitHub commit Patch Available

commit 7cb0e02389d8 (python-pillow/Pillow)

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

https://github.com/python-pillow/Pillow/commit/7cb0e02389d8aac2a60896a490f572db0b07b841

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhaii/vllm-cpu-rhel9:17934445542026-11-03redhat
redhatrhaii/model-opt-cuda-rhel9:17934443392026-11-03redhat
redhatrhaii/vllm-rocm-rhel9:17934444562026-11-03redhat
redhatrhaii/vllm-spyre-rhel9:17934444092026-11-03redhat
redhatrhaii/vllm-cuda-rhel9:17934446002026-11-03redhat
redhatrhaii/vllm-gaudi-rhel9:17934445102026-11-03redhat
pippillow @ 13.0.0 (fixes < 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
pillow1.0 ... 9.5.0 (107 versions)
  • every version 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 9× in last 7d / 29× 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 16:58 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-11-11 08:16 UTCEchelonGraph re-scored
  5. 2026-11-11 08:16 UTCVendor advisory
  6. 2026-11-11 08:16 UTCGHSA enrichmentGHSA-g842-9rc4-69pw · GitHub severity HIGH
  7. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-11-04 02:03 UTCEchelonGraph re-scored
  15. 2026-11-04 02:03 UTCGHSA enrichmentGHSA-g842-9rc4-69pw · GitHub severity HIGH
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-g842-9rc4-69pw · GitHub severity HIGH
  20. 2026-11-01 07:37 UTCEchelonGraph re-scored
  21. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 14 more
  1. 2026-10-27 14:29 UTCEchelonGraph re-scored▼ 0.60
  2. 2026-10-27 14:25 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  3. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-25 13:48 UTCEchelonGraph re-scored
  6. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-10-23 22:29 UTCEchelonGraph re-scored
  8. 2026-10-23 21:25 UTCEchelonGraph re-scored
  9. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-10-22 17:07 UTCEchelonGraph re-scored
  11. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-21 21:27 UTCEchelonGraph re-scored
  13. 2026-10-21 21:16 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  14. 2026-10-21 21:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-96637?
CVE-2026-96637 is a medium-severity vulnerability; its CVE record was published on October 21, 2026. Pillow is a Python imaging library. Prior to 13.0.0, SpiderImageFile.seek() in src/PIL/SpiderImagePlugin.py reparses a later SPIDER stack frame and replaces self._size without rerunning Image._decompression_bomb_check(). A tiny file can use a safe first frame to pass Image.open() and then declare…
When was the CVE record for CVE-2026-96637 published?
The CVE record for CVE-2026-96637 was published on October 21, 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-96637 actively exploited?
CVE-2026-96637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96637?
CVE-2026-96637 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-96637?
A fix for CVE-2026-96637 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-96637 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-96637

Explore →

Is Your Infrastructure Affected by CVE-2026-96637?

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