CVE-2026-115915

HIGHNVD 9.88.1
EchelonGraph scoreMEDIUM confidence

“▼” beside the score: it is lower than NVD's CVSS score.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-28. NVD baseline CVSS 9.8; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 6 sources updated this week

Also known asEUVD-2026-110035 (ENISA EUVD) · GHSA-h3rc-j82p-2c3h (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
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.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

vLLM is an inference and serving engine for large language models. Prior to 0.32.0, ImageMediaIO passes attacker-controlled image bytes to Pillow through Image.open(BytesIO(data)) without restricting decoder selection, and the MIME label does not constrain the selected format. Image-capable request paths through parse_image() and fetch_image() can therefore dispatch an EPS payload to host components. A host with Ghostscript affected by CVE-2024-29510 can execute commands with the vLLM process's privileges, while environments using Pillow 12.0.0 through 12.2.0 can trigger CVE-2026-59203 and exhaust media-loading workers. Deployments without the applicable vulnerable dependency are not affected by that corresponding impact. This issue is fixed in version 0.32.0.

CVSS v3
9.8
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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.7%
EPSS %ILE
51st
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.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% 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 26, 2026

Last Modified

October 28, 2026

Advisory Details (4)

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

Untrusted EPS inputs can trigger denial of service or Ghostscript RCE in vLLM · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-h3rc-j82p-2c3h
GitHub release Patch Available

v0.32.0

Patch available: vllm-project/vllm v0.32.0

https://github.com/vllm-project/vllm/releases/tag/v0.32.0
GitHub pull request

[Security] Restrict Pillow image formats on untrusted media paths

Fix merged in vllm-project/vllm PR #60022 on 2026-10-05 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/60022
GitHub commit

commit 710ac56e691d (vllm-project/vllm)

Fix landed in vllm-project/vllm commit 710ac56e691d — awaiting tagged release

https://github.com/vllm-project/vllm/commit/710ac56e691d4713feca50a43e6c440f07d373fd

Vendor Advisories for CVE-2026-115915(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
pipvllm @ 0.32.0 (fixes < 0.32.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)
PackageVulnerable rangeFix by version rangeDependents
vllm0.0.1 ... 0.9.2 (99 versions)
  • every version up to 0.32.0: fixed in 0.32.0
  • 0.30.0 up to 0.32.0: fixed in 0.32.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 20× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-11-01 11:29 UTCGHSA enrichmentGHSA-h3rc-j82p-2c3h · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-h3rc-j82p-2c3h · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-01 07:59 UTCEG score recompute▼ 1.70
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-31 12:36 UTCEG score recompute
  7. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-30 13:44 UTCEG score recompute
  9. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-29 14:38 UTCEG score recompute
  11. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-10-28 15:46 UTCEG score recompute▲ 1.70
  13. 2026-10-28 15:46 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  15. 2026-10-26 20:29 UTCEG score recompute
  16. 2026-10-26 19:47 UTCEG score recompute
  17. 2026-10-26 18:44 UTCEG score recompute
  18. 2026-10-26 18:01 UTCENISA EUVD ID recordedEUVD-2026-110035 · Source: ENISA EUVD
  19. 2026-10-26 17:23 UTCEG score recomputeFirst assessed: 8.1 HIGH
  20. 2026-10-26 17:20 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-115915?
CVE-2026-115915 is a high-severity vulnerability; its CVE record was published on October 26, 2026. vLLM is an inference and serving engine for large language models. Prior to 0.32.0, ImageMediaIO passes attacker-controlled image bytes to Pillow through Image.open(BytesIO(data)) without restricting decoder selection, and the MIME label does not constrain the selected format. Image-capable request…
When was the CVE record for CVE-2026-115915 published?
The CVE record for CVE-2026-115915 was published on October 26, 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-115915 actively exploited?
CVE-2026-115915 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-115915?
CVE-2026-115915 has a CVSS v3 base score of 9.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 8.1 (HIGH).
How do I remediate CVE-2026-115915?
A fix for CVE-2026-115915 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-115915 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-115915

Explore →

Is Your Infrastructure Affected by CVE-2026-115915?

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

Book a Demo →Browse All CVEs