{"answers":{"affected":"1 open source package ship an affected version, including vllm.","exploited":"There is no known exploitation of CVE-2026-130684 in the wild and no public exploit code.","exposure":"","fix":"Upgrade vllm to 0.33.0 or later.","what":"CVE-2026-130684 is a medium-severity vulnerability in vllm-project vllm, published on 18 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-130684 and fix it if it is affected.\n\nWhat it is: CVE-2026-130684 is a medium-severity vulnerability in vllm-project vllm, published on 18 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-130684 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vllm (PyPI): affected all versions; fixed in 0.33.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-130684/ (Markdown: https://insights.sbomify.com/CVE-2026-130684/index.md)","id":"CVE-2026-130684","markdown":"https://insights.sbomify.com/CVE-2026-130684/index.md","name":"CVE-2026-130684","record":{"aliases":["GHSA-9f95-xfwr-j77p","GHSA-qrj2-j723-m6w8"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"vLLM before 0.33.0 contains a path traversal vulnerability that allows malicious model publishers to redirect the served model and tokenizer by setting speculators_config verifier.name_or_path in config.json. Attackers can point this field at another local checkpoint directory to leak its tokenizer vocabulary via unauthenticated /detokenize requests and gain query access to private models.","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":false,"headline":"vLLM before 0.33.0 Path Traversal via speculators_config verifier.name_or_path","id":"CVE-2026-130684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":1,"n_vendor_status":0,"next":{"headline":"vLLM 0.28.0 before 0.33.0 Unauthenticated DoS via Out-of-Range Prompt Token ID","id":"CVE-2026-130685"},"nickname":null,"packages":[{"ecosystem":"PyPI","fixed":["0.33.0"],"introduced":["0"],"last_affected":[],"name_kind":null,"package":"vllm","purl":"pkg:pypi/vllm","purl_source":"cna","scope":"upstream","source":"CVE-2026-130684"}],"prev":{"headline":"SiYuan before 3.8.10 Path Traversal via /api/file/copyFile Deny-List Bypass","id":"CVE-2026-130683"},"products":["vllm"],"published":"2026-11-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-11-18","vendor_status":[],"vendors":["vllm-project"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-130684/"}