vLLM before 0.27.0 fails to properly classify DeepStream as a GPU backend and omits pixel-limit enforcement in its decode path. Unauthenticated attackers can activate DeepStream at request time to initialize the process-wide GPU decode pool and submit video that bypasses resource controls, causing partial denial of service for concurrent requests.
CVE-2026-78684
Score 5.3 from GitHub Security Advisory published 2026-08-25. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 27, 2026
Advisory Details (3)
Auto-updated Aug 25, 2026vLLM before 0.27.0 Denial of Service via DeepStream Backend | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vllm-before-denial-of-service-via-deepstream-backendcommit e23b19309b87 (vllm-project/vllm)
Fix landed in vllm-project/vllm commit e23b19309b87 — awaiting tagged release
https://github.com/vllm-project/vllm/commit/e23b19309b8705b21c3b3ff4129c9974ba15a419vLLM Unauthenticated Requests Exploit DeepStream Backend Confusion for DoS · Advisory · vllm-project/vllm · GitHub
https://github.com/vllm-project/vllm/security/advisories/GHSA-cqm8-jxg6-fqfqVendor Advisories for CVE-2026-78684(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 17:32 UTCEG score recompute
- 2026-08-29 17:32 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 17:29 UTCGHSA enrichment
- 2026-08-27 17:36 UTCEG score recompute
- 2026-08-27 17:36 UTCGHSA enrichment
- 2026-08-27 17:14 UTCEG score recompute
- 2026-08-27 17:14 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 11:59 UTCEG score recompute
- 2026-08-27 11:59 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 12:08 UTCEG score recompute
- 2026-08-26 12:08 UTCGHSA enrichment
- 2026-08-25 12:17 UTCEG score recompute
- 2026-08-25 11:42 UTCEG score recompute
- 2026-08-25 11:41 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-78684?
When was CVE-2026-78684 disclosed?
Is CVE-2026-78684 actively exploited?
What is the CVSS score of CVE-2026-78684?
How do I remediate CVE-2026-78684?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78684
Is Your Infrastructure Affected by CVE-2026-78684?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.