vLLM after 0.24.0 and before 0.31.0 contains a memory exhaustion vulnerability in MOSS-Audio model serving that caches a processor for every distinct request-controlled mm_processor_kwargs value in...

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0051, the 43rd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 21 Oct 2026, 01:17 UTC Confirmed by NVD
2. 4 Nov 2026, 11:00 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-823j-m4cj-hmjf
• OSV: GHSA-823j-m4cj-hmjf
• github.com/vllm-project/vllm/security/advisories/GHSA-823j-m4cj-hmjf
• www.vulncheck.com/advisories/vllm-0.25.0-before-0.31.0-moss-audio-memory-exhaustion-via-tokenize-mm-processor-kwargs

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.