CVE-2026-25960: SSRF Protection Bypass in vLLM
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.56% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: vllm (PyPI) 0.17.0, 0.14.1.
- Severity is disputed: the assigning authority (CNA) scores it 7.1, NVD 9.8.
Low priority for now. Upgrade to vllm (PyPI) 0.17.0, 0.14.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 9, 2026
- Updated
- Jul 21, 2026
- EPSS
- 0.5% · 47th percentile
- CWE
- CWE-918
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · GitHub_M
- 7.1
- 2.7 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vllm | vllm | cpe:2.3:a:vllm:vllm |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vllm vllm0.15.1 and later · before 0.17.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
vllm-project vllm
- >= 0.15.1, < 0.17.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | vllm | from 0.15.1 · before 0.17.0 | 0.17.0 |
| PyPI | vllm | before 0.14.1 | 0.14.1 |
Same product
vllm: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-22778vLLM leaks a heap address when PIL throws an error60This week
- CVE-2025-32444vLLM Vulnerable to Remote Code Execution via Mooncake Integration40Plan
- CVE-2024-11041Remote Code Execution in vllm-project/vllm40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-22807Jan 21, 2026 · vLLM affected by RCE via auto_map dynamic module loading during model initialization39Monitor
- ← EarlierCVE-2026-24779Jan 27, 2026 · vLLM vulnerable to Server-Side Request Forgery (SSRF) in `MediaConnector`28Monitor
- Later →CVE-2026-27893Mar 26, 2026 · vLLM's hardcoded trust_remote_code=True in NemotronVL and KimiK25 bypasses user security opt-out35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PyPI:vllm | 0.14.1 | Package registry (OSV) |
| PyPI:vllm | 0.17.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-116176230 days apartvLLM 0.9.2 before 0.24.0 SSRF via X-Request-Id in P2pNcclConnector35Monitor
- CVE-2026-2477941 days apartvLLM vulnerable to Server-Side Request Forgery (SSRF) in `MediaConnector`28Monitor
- CVE-2026-73560161 days apartvLLM: SSRF + arbitrary local file read in MiMoV2OmniMultiModalProcessor `_fetch_image` and audio loader bypass MediaConnector protections26Monitor
- CVE-2026-3475328 days apartvLLM affected by Server-Side Request Forgery (SSRF) in `download_bytes_from_url `21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- github.com/vllm-project/vllm/pull/34743
- github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfc
- access.redhat.com/errata/RHSA-2026:24977
- access.redhat.com/errata/RHSA-2026:42644
- access.redhat.com/security/cve/CVE-2026-25960
- bugzilla.redhat.com/show_bug.cgi?id=2445892
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25960.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.