Security Resilience

CVE-2026-90555

Vllm ≤ 0.28.0

Public PoC
Published
12 September 2026
Modified
16 September 2026
Patch / advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0052 44th percentile
Risk Priority 36 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-90555 is a high-severity Data Amplification (CWE-409) vulnerability in Vllm. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

vLLM versions before 0.28.0 fail to validate audio sample rate headers in the transcription endpoint, allowing authenticated clients to bypass duration checks. Attackers can submit forged FLAC headers with inflated sample rates to trigger excessive memory allocation and crash the…

more

API server process affecting all tenants.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-116175Same product: Vllm Vllm
CVE-2026-54233Same product: Vllm Vllm
CVE-2026-115912Same product: Vllm Vllm
CVE-2026-114051Same product: Vllm Vllm
CVE-2026-115915Same product: Vllm Vllm
CVE-2026-53923Same product: Vllm Vllm
CVE-2026-116180Same product: Vllm Vllm
CVE-2026-94627Same product: Vllm Vllm
CVE-2026-90553Same product: Vllm Vllm
CVE-2026-54235Same product: Vllm Vllm

Affected Assets

vllm
vllm
≤ 0.28.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

DoS protection limits the resource-exhaustion impact when a decompression bomb is processed.

Resource allocation controls bound memory/CPU consumption that a data-amplification attack would otherwise exhaust.

Input validation can reject or limit decompression of data whose expansion ratio exceeds safe thresholds.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure-development practices include input-validation and resource-limit checks that prevent improper handling of compressed data.

DE.CM-09 partial match
blocks

Runtime monitoring of compute resources can detect exhaustion caused by decompression bombs.

PR.IR-04 partial match
blocks

Capacity planning and monitoring directly limits the availability impact of data-amplification attacks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can uncover decompression-bomb vulnerabilities before release.

finds

Monitoring can detect anomalous resource usage but does not prevent the weakness.

prevents

Secure coding practices directly require bounds checking and safe handling of compressed data.

References