CVE-2026-22778

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 72% 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, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 4%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid image is sent to vLLM's multimodal endpoint, PIL throws an error. vLLM returns this error to the client, leaking a heap address. With this leak, we reduce ASLR from 4 billion guesses to ~8 guesses. This vulnerability can be chained a heap overflow with JPEG2000 decoder in OpenCV/FFmpeg to achieve remote code execution. This vulnerability is fixed in 0.14.1.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
88.9%
KEV
Not listed

Published

February 2, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 16, 2026
Patch available. Sources: github_pr, github_release, github, redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3462
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:3461
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:30089
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:30088
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:30087
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19712
github Patch Available

vLLM RCE In Video Processing · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-4r2x-xpjr-7cvv
github_release Patch Available

v0.14.1

Patch available: vllm-project/vllm v0.14.1

https://github.com/vllm-project/vllm/releases/tag/v0.14.1
github_pr

[Frontend] Standardize use of `create_error_response`

Fix merged in vllm-project/vllm PR #32319 on 2026-01-14 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/32319
github_pr

[Frontend] Improve error message

Fix merged in vllm-project/vllm PR #31987 on 2026-01-08 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/31987

Vendor Advisories for CVE-2026-22778(8)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-vllm-cpu-rhel9:17782643632026-05-20redhat
redhatrhoai/odh-vllm-rocm-rhel9:17720932372026-03-04redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17709560342026-03-04redhat
redhatrhaiis/vllm-rocm-rhel9:17721606252026-02-27redhat
redhatrhaiis/vllm-cuda-rhel9:17721605932026-02-27redhat

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 (18 versions)0.14.1—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-22778.yaml
    First seen Jan 1, 2026

    vLLM 0.8.3 - 0.14.0 - Information Disclosure

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-22778?
CVE-2026-22778 is a critical vulnerability published on February 2, 2026. vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid image is sent to vLLM's multimodal endpoint, PIL throws an error. vLLM returns this error to the client, leaking a heap address. With this leak, we reduce ASLR from 4 billion…
When was CVE-2026-22778 disclosed?
CVE-2026-22778 was first published in the National Vulnerability Database on February 2, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22778 actively exploited?
CVE-2026-22778 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 88.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-22778?
CVE-2026-22778 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-22778?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22778, 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-22778

Explore →

Is Your Infrastructure Affected by CVE-2026-22778?

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

Start Free Scan →Browse All CVEs