CVE-2026-27893
RCE in vLLM before 0.18.0 via malicious model repos, bypassing trust flag.
Is CVE-2026-27893 being exploited?
Not confirmed. CVE-2026-27893 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 1.3% probability of exploitation in the next 30 days.
How severe is CVE-2026-27893?
CVE-2026-27893 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-27893?
Yes. A fix has been recorded for CVE-2026-27893. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-27893 affect?
CVE-2026-27893 affects vLLM. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-27893?
Upgrade to vLLM 0.18.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution on server via malicious model repos, even if trust_remote_code opt-out is set.
Patch when possible
- affected>= 0.10.1 and < 0.18.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.