vLLM multimodal transport vulnerabilities can cause DoS and cache poisoning
Start here
On October 6, 2026, a GitHub security advisory disclosed trust boundary flaws in vLLM's scale-out multimodal transport: the transport treats caller-provided features as trusted rendering results and does not bind-validate them against the current model's rendering contract. Five flaws allow authenticated requests to cause shared engine crashes, cross-request encoder cache poisoning or disclosure, and loss of transport integrity. The advisory marks affected versions as before 0.30.0 and the fixed version as 0.30.0. The report was submitted by Patch the Planet (a collaboration between Trail of Bits and OpenAI) and discovered using GPT-5.5-Cyber.
Generated by AI from reports · Updated 2 days ago
Progress timeline
- GitHub 安全公告SelectedvLLM multimodal transmission trusts caller fields, 0.30.0 fixes crash and cache poisoning vulnerabilities
vLLM's scale-out multimodal transport treats caller-supplied features as trusted rendering results without binding validation against the current model's rendering contract. Five trust boundary flaws can let authenticated requests cause shared engine crashes, cross-request encoder cache poisoning or disclosure, and loss of transport integrity. Report submitted by Patch the Planet (a Trail of Bits and OpenAI collaboration), discovered using GPT-5.5-Cyber. The GitHub advisory marks affected versions as < 0.30.0 and the fixed version as 0.30.0.
Related discussion
Attention trend
New sources per day
- Oct 6New1 sources (1 outlets,0 accounts)
- Oct 7New0 sources (0 outlets,0 accounts)
- Oct 8New0 sources (0 outlets,0 accounts)
- Oct 9New0 sources (0 outlets,0 accounts)
- Oct 10New0 sources (0 outlets,0 accounts)
- Oct 11New0 sources (0 outlets,0 accounts)
- Oct 12New0 sources (0 outlets,0 accounts)
- Oct 13New0 sources (0 outlets,0 accounts)