{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-116179 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-116179 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-116179 is a high-severity vulnerability in Vllm Vllm, published on 25 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-116179 and fix it if it is affected.\n\nWhat it is: CVE-2026-116179 is a high-severity vulnerability in Vllm Vllm, published on 25 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-116179 in the wild and no public exploit code.\n\nAffected product: Vllm Vllm. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-116179/ (Markdown: https://insights.sbomify.com/CVE-2026-116179/index.md)","id":"CVE-2026-116179","markdown":"https://insights.sbomify.com/CVE-2026-116179/index.md","name":"CVE-2026-116179","record":{"aliases":["GHSA-4m6g-h9mv-wqjc","GHSA-6vc9-vh4h-cxh4"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[{"product":"vllm","vendor":"vllm"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"vLLM from 0.18.0 before 0.31.0 contains a resource exhaustion vulnerability that allows API clients to bypass the video/jpeg frame-count cap by overriding num_frames through media_io_kwargs. Attackers can set num_frames to -1 with a large inline video so VideoMediaIO.load_base64 decodes every frame, exhausting memory and crashing the API frontend.","ecosystems":[],"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 0.18.0 before 0.31.0 Memory Exhaustion via media_io_kwargs num_frames Override","id":"CVE-2026-116179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vllm:vllm","products":["vllm:vllm"],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"vLLM from 0.8.5 before 0.31.0 Cross-Tenant DoS via Uninitialized LogprobsTensors","id":"CVE-2026-116180"},"packages":[],"prev":{"headline":"vLLM 0.20.0 before 0.30.0 DoS via /inference/v1/generate mm_placeholders","id":"CVE-2026-116178"},"products":["vllm"],"published":"2026-10-25","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":"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-26","vendors":["vllm-project"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-116179/"}