{"cve":{"cve_id":"CVE-2026-47155","is_kev":false,"kev_date_added":null,"kev_vendor_project":null,"kev_product":null,"kev_vulnerability_name":null,"kev_short_description":null,"kev_required_action":null,"kev_due_date":null,"kev_known_ransomware":null,"kev_notes":null,"kev_cwes":null,"epss_score":0.00142,"epss_percentile":0.03795,"epss_as_of":"2026-06-23","description":"vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.0, vLLM's revision pinning controls do not consistently apply to all artifacts loaded for a model. A deployment that supplies --revision or --code-revision can still load dynamic code, GGUF files, image processors, retrieval side weights, or same-repository subfolder weights/config from an unpinned/default revision. This is a supply-chain integrity issue for pinned vLLM deployments. Operators can believe they are serving a reviewed model revision while vLLM resolves behavior-affecting nested or sibling artifacts outside that reviewed revision. This vulnerability is fixed in 0.22.0.","published_at":"2026-06-22T22:20:10.793000Z","last_modified_at":null,"cvss_v3_score":6.5,"cvss_v3_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N","cvss_v3_severity":"MEDIUM","cvss_v4_score":null,"cvss_v4_vector":null,"cvss_v4_severity":null,"ssvc_decision":null,"ssvc_exploitation":null,"ssvc_automatable":null,"ssvc_technical_impact":null,"cwes":["CWE-345"],"nvd_references":["https://github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gm","https://github.com/vllm-project/vllm/pull/42616","https://github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6","https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac"],"vuln_status":null,"trending_score":null,"is_trending":false,"has_trended":false,"trended_number_one":false,"trending_peak_score":null,"trending_peak_rank":null,"started_trending_at":null,"trended_number_one_at":null,"summary_generated":null,"summary_generated_at":null,"summary_model":null,"created_at":"2026-06-24T00:09:39.878444Z","updated_at":"2026-06-28T23:30:40.878937Z"},"effective_severity":"MEDIUM","badges":[],"impact_analysis":[],"cvss_v3_decoded":{"version":"3.1","metrics":[{"metric":"AV","name":"Attack Vector","value":"N","value_label":"Network"},{"metric":"AC","name":"Attack Complexity","value":"H","value_label":"High"},{"metric":"PR","name":"Privileges Required","value":"N","value_label":"None"},{"metric":"UI","name":"User Interaction","value":"N","value_label":"None"},{"metric":"S","name":"Scope","value":"U","value_label":"Unchanged"},{"metric":"C","name":"Confidentiality","value":"L","value_label":"Low"},{"metric":"I","name":"Integrity","value":"H","value_label":"High"},{"metric":"A","name":"Availability","value":"N","value_label":"None"}]},"cvss_v4_decoded":{"version":null,"metrics":[]},"affected":[{"vendor_slug":"vllm-project","vendor_name":"vllm-project","product_slug":"vllm","product_name":"vllm","version_start":"< 0.22.0","version_start_inclusive":true,"version_end":"< 0.22.0","version_end_inclusive":true,"cpe23_uri":"cve5:vllm-project:vllm:< 0.22.0:< 0.22.0"}],"exploit_refs":[],"news":[],"references":[{"url":"https://github.com/vllm-project/vllm/security/advisories/GHSA-3ww4-5jv9-j5gm","source_type":"VENDOR_ADVISORY","tags":["advisory"]},{"url":"https://github.com/vllm-project/vllm/pull/42616","source_type":"PATCH","tags":["patch"]},{"url":"https://github.com/vllm-project/vllm/commit/d26a28ab033697f55a1414b5b0435de7cd6045b6","source_type":"PATCH","tags":["patch"]},{"url":"https://huntr.com/bounties/3f1e24c0-87d2-4f6c-a705-820f380879ac","source_type":"MISC","tags":[]}],"timeline":[{"type":"published","at":"2026-06-22T22:20:10.793000Z","label":"CVE published","source":null},{"type":"cvss_changed","at":"2026-06-28T17:54:57.553414Z","label":"CVSS score revised","source":"cvelistv5"},{"type":"cvss_changed","at":"2026-06-28T17:54:57.553414Z","label":"CVSS score revised","source":"cvelistv5"},{"type":"cvss_changed","at":"2026-06-28T17:54:57.553414Z","label":"CVSS score revised","source":"cvelistv5"}]}