vllm-project · vLLM · published 2026-03-09

CVE-2026-25960SSRF Protection Bypass in vLLM

Routine No exploitation evidence; EPSS 0.6%.

CVE-2026-25960 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 49% of all CVEs. This vLLM vulnerability: CVSS 7.1 (v3.1). Fixed upstream in vLLM 0.17.0. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in vLLM 0.17.0.

Patch events

  1. This monthSecurity release

    AI toolingvLLM

    vLLM security release: 0.17.0

    Upgrade to 0.17.0

    Why: Vendor security release for server software (most severe: CVE-2026-25960).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.6% (50th pct)FIRST EPSS v2026.06.15
CVSS base score7.1 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

vLLM is an inference and serving engine for large language models (LLMs). The SSRF protection fix for CVE-2026-24779 add in 0.15.1 can be bypassed in the load_from_url_async method due to inconsistent URL parsing behavior between the validation layer and the actual HTTP client. The SSRF fix uses urllib3.util.parse_url() to validate and extract the hostname from user-provided URLs. However, load_from_url_async uses aiohttp for making the actual HTTP requests, and aiohttp internally uses the yarl library for URL parsing. This vulnerability in 0.17.0.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →