CVE-2026-5497
Vllm denial of service
- Published11 Jun 2026
Description
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-5497
- https://bugzilla.redhat.com/show_bug.cgi?id=2487813
- https://github.com/vllm-project/vllm/commit/58ee61422169ce17e08248f8efa1e9df434fe395
- https://huntr.com/bounties/7bd92629-b396-4449-8f88-6c0092530eb4
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5497.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-5497 being actively exploited?
CVE-2026-5497 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.90%.
How severe is CVE-2026-5497?
CVE-2026-5497 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.90% probability of exploitation.
Which products are affected by CVE-2026-5497?
Affected products include Vllm.
How do I fix CVE-2026-5497?
Upgrade affected software to a fixed version, for example Vllm 0.19.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-5497 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.