Pillow is a Python imaging library. From 9.4.0 until 13.0.0, ImagingJpegEncode() in src/libImaging/JpegEncode.c can call jpeg_write_marker() for a JPEG COM comment when an ICC profile has exactly filled the 65536-byte encoder buffer. libjpeg writes one byte before checking the exhausted free_in_buffer counter, which then wraps and permits the attacker-controlled comment and subsequent compressed image data to overwrite adjacent heap memory. Re-saving an untrusted image as JPEG while preserving its ICC profile and forwarded comment can crash the process and may enable code execution in suitable runtime and heap layouts. This issue is fixed in version 13.0.0.
CVE-2026-96778
HIGHNVD 8.88.8Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (39th 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-107566 (ENISA EUVD) · GHSA-g7cr-3p24-7wf7 (GitHub Security Advisories)Source: ENISA EUVD
8.8EG
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.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 40EG Risk 40/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)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 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.5%
- EPSS %ILE
- 39th
- 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.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 21, 2026
Last Modified
October 28, 2026
Advisory Details (4)
Auto-updated Oct 21, 2026Patch available. Sources: github, github_pr, github_commit, github_release.
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.0GitHub commit Patch Available
commit 02561b8dc611 (python-pillow/Pillow)
Patch available: python-pillow/Pillow 13.0.0 (contains commit 02561b8dc611)
https://github.com/python-pillow/Pillow/commit/02561b8dc6117d5670d4b469fecdd02c70854f9bGitHub pull request Patch Available
Check COM marker length when encoding JPEG
Patch available: python-pillow/Pillow 13.0.0 (PR #10124 merged 2026-10-05)
https://github.com/python-pillow/Pillow/pull/10124GitHub advisoryMentions a patch (unverified)
Heap buffer overflow writing JPEG comment after ICC profile fills buffer · Advisory · python-pillow/Pillow · GitHub
https://github.com/python-pillow/Pillow/security/advisories/GHSA-g7cr-3p24-7wf7Vendor Advisories for CVE-2026-96778(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:92861Red Hat Product SecurityCritical
Red Hat Security Advisory: Satellite 6.19 security update
- RHSA-2026:92510Red Hat Product SecurityCritical
Red Hat Security Advisory: RHOAI 3.4.6 - Red Hat OpenShift AI
- GHSA-g7cr-3p24-7wf7GitHub Security AdvisoriesHigh
Pillow: Heap buffer overflow writing JPEG comment after ICC profile fills buffer
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | Pillow @ 13.0.0 (fixes >= 9.4.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
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| pillow | 10.0.0 ... 9.5.0 (17 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 21× 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 it from the CNA feed. 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). Most recent first.
- 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-11-01 07:37 UTCGHSA enrichmentGHSA-g7cr-3p24-7wf7 · GitHub severity HIGH
- 2026-11-01 07:37 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-28 02:01 UTCEG score recompute
- 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-27 14:47 UTCEG score recompute▲ 1.10
- 2026-10-27 14:46 UTCNVD updateCVSS v3 → 8.8
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-25 13:48 UTCEG score recompute
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-22 17:07 UTCEG score recompute
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-21 21:27 UTCEG score recompute
- 2026-10-21 21:02 UTCEG score recomputeFirst assessed: 7.7 HIGH
- 2026-10-21 21:02 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:pillow
Frequently asked(5)
What is CVE-2026-96778?
CVE-2026-96778 is a high-severity vulnerability; its CVE record was published on October 21, 2026. Pillow is a Python imaging library. From 9.4.0 until 13.0.0, ImagingJpegEncode() in src/libImaging/JpegEncode.c can call jpeg_write_marker() for a JPEG COM comment when an ICC profile has exactly filled the 65536-byte encoder buffer. libjpeg writes one byte before checking the exhausted…
When was the CVE record for CVE-2026-96778 published?
The CVE record for CVE-2026-96778 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 28, 2026; the record at its source may have been updated since.
Is CVE-2026-96778 actively exploited?
CVE-2026-96778 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96778?
CVE-2026-96778 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-96778?
A fix for CVE-2026-96778 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-96778 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-96778
Is Your Infrastructure Affected by CVE-2026-96778?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.