API server crash via forged FLAC sample rate
Published Sep 12, 2026 · Updated Sep 12, 2026
Denial of service in vLLM before 0.28.0 allows remote authenticated users to crash the API server via a forged FLAC header. The soundfile path calculates duration by dividing frame count by the untrusted header sample rate, then reads decoded float32 PCM into memory. Exploitation requires a transcription-capable model, audio dependencies, and a valid API key; one request can exhaust process memory and interrupt service for all tenants.
Summary
What happened
Denial of service in vLLM before 0.28.0 allows remote authenticated users to crash the API server via a forged FLAC header. The soundfile path calculates duration by dividing frame count by the untrusted header sample rate, then reads decoded float32 PCM into memory. Exploitation requires a transcription-capable model, audio dependencies, and a valid API key; one request can exhaust process memory and interrupt service for all tenants.
The record
- CVE
- CVE-2026-90555
- Published
- Sep 12, 2026
- Updated
- Sep 12, 2026
- Vendor
- vLLM Project
- Product
- vLLM
- Classifications
- CWE-1284, CWE-807, CWE-409, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 12, 2026CVE publishedPublication date reported by the CVE source.
- Sep 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.28.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo