CVE-2026-22807
Startup-time RCE via untrusted auto_map modules in vLLM.
Is CVE-2026-22807 being exploited?
Not confirmed. CVE-2026-22807 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.76% probability of exploitation in the next 30 days.
How severe is CVE-2026-22807?
CVE-2026-22807 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-22807?
Yes. A fix has been recorded for CVE-2026-22807. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22807 affect?
CVE-2026-22807 affects vLLM (versions <0.14.0), Servers hosting vLLM deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22807?
Upgrade to vLLM 0.14.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary Python code execution on vLLM host during model load if attacker controls model repo/path.
Patch when possible
- affected>= 0.10.1 and < 0.14.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.