CVE-2026-54236

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 41% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, the fix for CVE-2026-22778, which introduced a sanitize_message helper that strips object-repr memory addresses from error messages before they reach the client, is incomplete: several response paths echo str(exc) directly to clients without calling sanitize_message. The unsanitized sites include the Anthropic API router in vllm/entrypoints/anthropic/api_router.py (the POST /v1/messages and POST /v1/messages/count_tokens handlers), the Server-Sent Events streaming converter in vllm/entrypoints/anthropic/serving.py, and the realtime speech-to-text WebSocket in vllm/entrypoints/speech_to_text/realtime/connection.py. These paths catch the exception inside the route coroutine and construct the JSONResponse themselves, bypassing the sanitizing global FastAPI exception handler, and WebSocket frames do not traverse that handler chain at all. Using the same primitive as the parent issue, an unauthenticated attacker can send malformed image bytes through the Anthropic Messages API image content parts so that PIL.Image.open raises an UnidentifiedImageError whose message contains the BytesIO object repr, leaking the heap memory address verbatim in the error.message field of the response body. This vulnerability is fixed in 0.23.1rc0.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

Published

June 17, 2026

Last Modified

June 24, 2026

Advisory Details (3)

Auto-updated Jun 23, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github, github_pr.
github_commit

commit 949236297293 (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/94923629729381d7f7c9efde72071a2441f7fd82
github_pr

[Security] Apply sanitize_message to Anthropic and STT error paths

Fix merged in vllm-project/vllm PR #45119 on 2026-06-11 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/45119
githubMentions a patch (unverified)🟡 PoC Available

vLLM: incomplete CVE-2026-22778 fix leaks PIL repr addresses via Anthropic router (CWE-532) · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-hgg8-fqqc-vfmw

Vendor Advisories for CVE-2026-54236(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—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 (89 versions)
  • every version up to 0.24.0: fixed in 0.24.0
  • every version through 0.23.0: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 06:09 UTCOSV refresh
  10. 2026-10-02 17:56 UTCEPSS rescore
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-09-30 15:03 UTCEPSS rescore
  13. 2026-09-29 15:22 UTCEPSS rescore
  14. 2026-09-28 13:51 UTCEPSS rescore
  15. 2026-09-27 13:48 UTCEPSS rescore
  16. 2026-09-26 15:59 UTCEPSS rescore
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-17 19:31 UTCEPSS rescore
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-14 03:08 UTCEG score recompute
  25. 2026-09-13 16:47 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 22:26 UTCEG score recompute
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-25 06:16 UTCEG score recompute
  18. 2026-08-23 04:29 UTCEG score recompute
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 07:24 UTCEG score recompute
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-20 08:16 UTCEG score recompute
  24. 2026-08-19 17:04 UTCEPSS rescore
  25. 2026-08-19 08:12 UTCEG score recompute
  26. 2026-08-18 13:48 UTCEPSS rescore
  27. 2026-08-17 15:27 UTCEG score recompute
  28. 2026-08-17 13:47 UTCEPSS rescore
  29. 2026-08-16 16:20 UTCEG score recompute
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 02:14 UTCEPSS rescore
  32. 2026-08-15 17:17 UTCEG score recompute
  33. 2026-08-15 01:30 UTCEPSS rescore
  34. 2026-08-14 18:10 UTCEG score recompute
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-12 17:54 UTCEG score recompute
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-11 18:52 UTCEG score recompute
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-09 20:49 UTCEG score recompute
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-08 21:48 UTCEG score recompute
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-07 22:46 UTCEG score recompute
  45. 2026-08-06 23:45 UTCEG score recompute
  46. 2026-08-06 13:47 UTCEPSS rescore
  47. 2026-08-06 00:43 UTCEG score recompute
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-05 01:42 UTCEG score recompute
  50. 2026-08-04 15:10 UTCEPSS rescore
  51. 2026-08-04 10:39 UTCEPSS rescore
  52. 2026-08-04 02:28 UTCEG score recompute
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-02 04:25 UTCEG score recompute
  55. 2026-08-02 02:27 UTCEPSS rescore
  56. 2026-08-01 05:23 UTCEG score recompute
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-31 03:57 UTCEG score recompute
  59. 2026-07-30 16:28 UTCEPSS rescore
  60. 2026-07-30 03:43 UTCEG score recompute
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-29 02:17 UTCEG score recompute
  63. 2026-07-28 15:37 UTCEPSS rescore
  64. 2026-07-27 18:12 UTCEG score recompute
  65. 2026-07-26 19:10 UTCEG score recompute
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-24 14:18 UTCEPSS rescore
  69. 2026-07-23 14:18 UTCEPSS rescore
  70. 2026-07-23 03:19 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-21 15:25 UTCEPSS rescore
  73. 2026-07-20 17:08 UTCEPSS rescore
  74. 2026-07-19 14:31 UTCEPSS rescore
  75. 2026-07-19 14:31 UTCEPSS rescore

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-54236.yaml
    Published Jun 22, 2026

    vLLM <= 0.23.0 - Anthropic Router Heap Address Information Leak

    Open source ↗

Frequently asked(5)

What is CVE-2026-54236?
CVE-2026-54236 is a medium vulnerability published on June 17, 2026. vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, the fix for CVE-2026-22778, which introduced a sanitizemessage helper that strips object-repr memory addresses from error messages before they reach the client, is incomplete: several response paths echo…
When was CVE-2026-54236 disclosed?
CVE-2026-54236 was first published on June 17, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54236 actively exploited?
CVE-2026-54236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54236?
CVE-2026-54236 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54236?
A fix for CVE-2026-54236 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54236 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-54236

Explore →

Is Your Infrastructure Affected by CVE-2026-54236?

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