vLLM Vulnerable to Denial of Service by Abusing XGrammar Cache
vLLM, XGrammar
vLLM was found vulnerable to denial of service attacks through the XGrammar structured output cache. Users were advised to update affected components.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- fix status
- Fix status unknown
- first report
- 15 Apr 2025
- last update
- 15 Apr 2025
Timeline · 1
Sources · 1
Advisories and databases
- 2025-04-15GHSA-hf3c-wxg2-49q9: vLLM vulnerable to Denial of Service by abusing xgrammar cacheGitHub Advisory Database · github.com/advisories/GHSA-hf3c-wxg2-49q9
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 15 Apr 2025 · first reported 15 Apr 2025
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 07:00Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# vLLM Vulnerable to Denial of Service by Abusing XGrammar Cache https://gcdradar.vercel.app/incidents/vllm-vulnerable-to-denial-of-service-by-abusing-xgrammar-cac · AIR-2025-0271 · closed 2025-04-15 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2025-04-15 - AI role: Attack on AI - Products: vLLM, XGrammar ## Summary vLLM was found vulnerable to denial of service attacks through the XGrammar structured output cache. Users were advised to update affected components. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2025-04-15: GHSA-hf3c-wxg2-49q9: vLLM vulnerable to Denial of Service by abusing xgrammar cache (https://github.com/advisories/GHSA-hf3c-wxg2-49q9) ## Sources - 2025-04-15 GitHub Advisory Database: GHSA-hf3c-wxg2-49q9: vLLM vulnerable to Denial of Service by abusing xgrammar cache https://github.com/advisories/GHSA-hf3c-wxg2-49q9 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.0vLLM CVE-2025-30165: Remote Code Execution in vLLM Multi-Node Cluster Configuration
Patch now · Disclosed · since 6 May 2025 · CVE-2025-30165
AI - closed6.5vLLM CVE-2025-46560: vLLM vulnerable to denial of service via quadratic time complexity
Patch now · Disclosed · since 29 Apr 2025 · updated 30 Apr 2025 · CVE-2025-46560
AI - closed10.0vLLM CVE-2025-32444: vLLM Remote Code Execution via Mooncake Integration
Patch now · Disclosed · since 29 Apr 2025 · updated 30 Apr 2025 · CVE-2025-32444
AI - closed7.5vLLM CVE-2025-30202: Data Exposure via ZeroMQ in Multi-Node vLLM Deployment
Patch now · Disclosed · since 29 Apr 2025 · updated 30 Apr 2025 · CVE-2025-30202
AI - closed9.8vLLM CVE-2024-11041: vLLM Deserialization of Untrusted Data vulnerability
Patch now · Disclosed · since 20 Mar 2025 · CVE-2024-11041
AI - closed9.8vLLM CVE-2024-9053: vLLM Pickle Deserialization Remote Code Execution
Patch now · Disclosed · since 20 Mar 2025 · CVE-2024-9053
AI