CVE-2026-5497

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-11. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

vLLM versions 0.8.0 and later are vulnerable to an Out-of-Memory (OOM) Denial of Service (DoS) attack due to unbounded frame count processing in the VideoMediaIO.load_base64() method. When processing video/jpeg data URLs, the method splits the base64 data string on commas to extract individual JPEG frames without enforcing a frame count limit. An attacker can exploit this by crafting a single API request containing thousands of comma-separated base64-encoded JPEG frames in a data URL, causing the server to decode all frames into memory and crash due to excessive memory consumption. This vulnerability is reachable via the OpenAI-compatible chat completions API and does not require authentication.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 11, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/7bd92629-b396-4449-8f88-6c0092530eb4
github_commit

commit 58ee61422169 (vllm-project/vllm)

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

https://github.com/vllm-project/vllm/commit/58ee61422169ce17e08248f8efa1e9df434fe395

Vendor Advisories for CVE-2026-5497(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhelai3/disk-image-cuda-rhel9:17828049572026-06-30redhat
redhatrhelai3/bootc-rocm-rhel9:17827448302026-06-30redhat

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 rangeFixed inDependents
vllm0.10.0 ... 0.9.2 (29 versions)0.19.0—

Weakness Classification(2)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 89× 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 240 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5497?
CVE-2026-5497 is a high vulnerability published on June 11, 2026. vLLM versions 0.8.0 and later are vulnerable to an Out-of-Memory (OOM) Denial of Service (DoS) attack due to unbounded frame count processing in the VideoMediaIO.load_base64() method. When processing video/jpeg data URLs, the method splits the base64 data string on commas to extract individual JPEG…
When was CVE-2026-5497 disclosed?
CVE-2026-5497 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5497 actively exploited?
CVE-2026-5497 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.1% of all scored CVEs.
What is the CVSS score of CVE-2026-5497?
CVE-2026-5497 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-5497?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5497, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-5497

Explore →

Is Your Infrastructure Affected by CVE-2026-5497?

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

Start Free Scan →Browse All CVEs