Security readout for executives and security teams
Plain-English summary
CVE-2026-25960 is a high-severity vLLM server-side request forgery protection bypass. An authenticated or otherwise low-privileged user who can supply a URL to affected vLLM functionality may cause the server to request unintended internal resources. The main business risk is exposure of internal data or services from AI infrastructure.
Executive priority
Prioritize remediation for internet-facing, multi-tenant, or internally privileged vLLM services. The issue is not listed as actively exploited in the supplied sources, but the confidentiality impact makes delayed patching risky.
Technical view
The issue affects vLLM versions >= 0.15.1 and < 0.17.0. The prior SSRF fix validates URLs with urllib3 parsing, but load_from_url_async performs requests through aiohttp/yarl, creating inconsistent hostname interpretation. CVSS 3.1 is 7.1: network attack, low complexity, low privileges, no user interaction, high confidentiality impact, low availability impact.
Likely exposure
Most relevant exposure is vLLM deployments in the affected version range that let users or tenants provide URLs for model, asset, or remote-loading workflows.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. Exploitation requires access to a vulnerable URL-loading path and may target internal network resources reachable by the vLLM server.
Researcher notes
Focus review on URL parser differentials between validation and request execution. The supplied record ties this to the earlier CVE-2026-24779 SSRF fix and load_from_url_async. Avoid assuming other vLLM components are affected without vendor evidence.
Mitigation direction
- Upgrade vLLM outside the affected range, preferably 0.17.0 or later if vendor guidance confirms.
- Review the GitHub advisory and Red Hat advisories for product-specific fixed builds.
- Restrict URL-loading features to trusted users until patched.
- Block vLLM server egress to internal metadata and sensitive service networks.
- Add allowlists for approved remote hosts where operationally feasible.
Validation and detection
- Inventory vLLM versions and flag >= 0.15.1 and < 0.17.0.
- Identify services exposing URL-loading workflows to users, tenants, or API clients.
- Review logs for unexpected outbound requests from vLLM hosts to internal addresses.
- Confirm patched package versions against vendor advisories, not only application metadata.
- Test egress controls from vLLM hosts to sensitive internal destinations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-474: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-25960 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L2.84.2GitHub_MCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L2.84.2redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-09T22:02:05.461Z: Reported to Red Hat.
- 2026-03-09T21:01:01.827Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/vllm-project/vllm/security/advisories/GHSA-v359-jj2v-j536CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/vllm-project/vllm/security/advisories/GHSA-qh4c-xf7m-gxfcCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vllm-project/vllm/pull/34743CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vllm-project/vllm/commit/6f3b2047abd4a748e3db4a68543f8221358002c0CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-25960CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2445892CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25960.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:42644CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:24977CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Function with Inconsistent Implementations
Use of Function with Inconsistent Implementations represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.