{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-114054 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-114054 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-114054 is a high-severity vulnerability in vllm-project vllm, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114054 and fix it if it is affected.\n\nWhat it is: CVE-2026-114054 is a high-severity vulnerability in vllm-project vllm, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-114054 in the wild and no public exploit code.\n\nAffected product: vllm-project 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-114054/ (Markdown: https://insights.sbomify.com/CVE-2026-114054/index.md)","id":"CVE-2026-114054","markdown":"https://insights.sbomify.com/CVE-2026-114054/index.md","name":"CVE-2026-114054","record":{"aliases":["GHSA-72rf-5fg2-rm98","GHSA-rh6f-3x46-j33q"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"vLLM before 0.31.0 contains a cache aliasing vulnerability that allows authenticated attackers to collide shared cache keys by supplying caller-controlled values such as EXIF ImageID or cache_salt. Attackers can set a UUID EXIF ImageID to receive another request's cached processed media, or match cache_salt to a LoRA name to reuse first-block KV state.","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 before 0.31.0 Cross-Request Cache Aliasing via EXIF ImageID and Prefix-Cache Keys","id":"CVE-2026-114054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"vLLM 0.7.3 before 0.31.0 DoS via Unvalidated mm_processor_kwargs","id":"CVE-2026-114055"},"packages":[],"prev":{"headline":"vLLM 0.7.3 before 0.31.0 RCE via mm_processor_kwargs.code_revision","id":"CVE-2026-114053"},"products":["vllm"],"published":"2026-10-21","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-10-28","vendors":["vllm-project"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114054/"}