{"answers":{"affected":"3 open source packages ship an affected version, including vllm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25960 in the wild and no public exploit code.","fix":"Upgrade vllm to 0.17.0 or later.","what":"CVE-2026-25960 is a high-severity server-side request forgery vulnerability in Vllm Vllm, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25960 and fix it if it is affected.\n\nWhat it is: CVE-2026-25960 is a high-severity server-side request forgery vulnerability in Vllm Vllm, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25960 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vllm (PyPI): affected from 0.15.1; fixed in 0.17.0\n- vllm (PyPI): affected from 0.15.1; fixed in 0.17.0\n- vllm (PyPI): affected from 0.15.1; fixed in 0.17.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25960/ (Markdown: https://insights.sbomify.com/CVE-2026-25960/index.md)","id":"CVE-2026-25960","markdown":"https://insights.sbomify.com/CVE-2026-25960/index.md","name":"CVE-2026-25960","record":{"aliases":["GHSA-v359-jj2v-j536","PYSEC-2026-3411"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LLM inference engine","requires_auth":"low_privilege","summary":"Attackers can bypass SSRF protections in vLLM by exploiting inconsistent URL parsing between validation and request libraries, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vllm","vendor":"vllm"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-474","name":"Use of Function with Inconsistent Implementations"},{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SSRF Protection Bypass in vLLM","id":"CVE-2026-25960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"vllm:vllm","products":["vllm:vllm"],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"SumatraPDF Update MITM -\u003e Arbitrary Code Execution","id":"CVE-2026-25961"},"packages":[{"ecosystem":"PyPI","fixed":["0.17.0"],"introduced":["0.15.1"],"last_affected":[],"package":"vllm","purl":null,"source":"GHSA-v359-jj2v-j536"},{"ecosystem":"PyPI","fixed":["0.17.0"],"introduced":["0.15.1"],"last_affected":[],"package":"vllm","purl":"pkg:pypi/vllm","source":"GHSA-v359-jj2v-j536"},{"ecosystem":"PyPI","fixed":["0.17.0"],"introduced":["0.15.1"],"last_affected":[],"package":"vllm","purl":"pkg:pypi/vllm","source":"PYSEC-2026-3411"}],"prev":{"headline":"FreeRDP has heap-use-after-free in xf_cliprdr_provide_data_","id":"CVE-2026-25959"},"products":["vllm"],"published":"2026-03-09","related":[{"cvss_score":10,"headline":"vLLM Vulnerable to Remote Code Execution via Mooncake Integration","id":"CVE-2025-32444","kev_date_added":null,"published":"2025-04-30"},{"cvss_score":9.8,"headline":"vLLM leaks a heap address when PIL throws an error","id":"CVE-2026-22778","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":9.8,"headline":"vLLM Allows Remote Code Execution via PyNcclPipe Communication Service","id":"CVE-2025-47277","kev_date_added":null,"published":"2025-05-20"},{"cvss_score":9.8,"headline":"Remote Code Execution in vllm-project/vllm","id":"CVE-2024-11041","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.1,"headline":"vLLM: OpenAI auth bypass","id":"CVE-2026-48746","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":9.1,"headline":"vLLM Allows Remote Code Execution via Mooncake Integration","id":"CVE-2025-29783","kev_date_added":null,"published":"2025-03-19"},{"cvss_score":8.8,"headline":"vLLM 0.9.2 before 0.24.0 SSRF via X-Request-Id in P2pNcclConnector","id":"CVE-2026-116176","kev_date_added":null,"published":"2026-10-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-21","vendors":["vllm-project"]},"summary":"Attackers can bypass SSRF protections in vLLM by exploiting inconsistent URL parsing between validation and request libraries, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2026-25960/"}