在 vLLM 0.31.0 之前的版本中,系统会原样使用客户端提供的多模态 UUID 作为缓存标识,且未对缓存命中进行一致性检查,从而导致引擎崩溃。未经身份验证的攻击者可以通过使 P0/P1 处理器的缓存不同步,触发致命的 token 占位符不匹配,致使整个服务实例终止,直至重启才能恢复。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| vllm-project | vllm | 0 ~ 0.31.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-114053 | 8.1 HIGH | vLLM 0.7.3 before 0.31.0 RCE via mm_processor_kwargs.code_revision |
| CVE-2026-114055 | 7.5 HIGH | vLLM 0.7.3 before 0.31.0 DoS via Unvalidated mm_processor_kwargs |
| CVE-2026-114052 | 7.5 HIGH | vLLM 0.25.0 before 0.31.0 MOSS-Audio Memory Exhaustion via /tokenize mm_processor_kwargs |
| CVE-2026-114051 | 7.5 HIGH | vLLM before 0.31.0 Denial of Service via min_tokens in /inference/v1/generate |
| CVE-2026-114054 | 6.5 MEDIUM | vLLM before 0.31.0 Cross-Request Cache Aliasing via EXIF ImageID and Prefix-Cache Keys |
| CVE-2026-114049 | 3.7 LOW | vLLM before 0.31.0 Stale allowed_token_ids Mask via InputBatch.condense |
No comments yet