GHSA-MCMC-2M55-J8JJ

The fix here for CVE-2025-62164 is not sufficient. The fix only disables prompt embeds by default rather than addressing the root cause, so the DoS vulnerability remains when the feature is enabled.

Details

vLLM's pending change attempts to fix the root cause, which is the missing sparse tensor validation. PyTorch (~v2.0) disables sparse tensor validation (specifically, sparse tensor invariants checks) by default for performance reasons. vLLM is adding the sparse tensor validation to ensure indices are valid, non-negative, and within bounds. These checks help catch malformed tensors.

PoC

NA

Changes

• https://github.com/vllm-project/vllm/pull/30649

Current fix only added a flag to disable/enable prompt embeds, so by default, prompt embeds feature is disabled in vLLM, which stops DoS attacks through the embeddings. However, It doesn’t address the problem when the flag is enabled and there is still potential for DoS attacks.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

GHSA-MCMC-2M55-J8JJ has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.13.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-MCMC-2M55-J8JJ? GHSA-MCMC-2M55-J8JJ is a high-severity improper input validation vulnerability in vllm (pip), affecting versions >= 0.10.2, < 0.11.1. It is fixed in 0.13.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is GHSA-MCMC-2M55-J8JJ? GHSA-MCMC-2M55-J8JJ has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of vllm are affected by GHSA-MCMC-2M55-J8JJ? vllm (pip) versions >= 0.10.2, < 0.11.1 is affected.
4. Is there a fix for GHSA-MCMC-2M55-J8JJ? Yes. GHSA-MCMC-2M55-J8JJ is fixed in 0.13.0. Upgrade to this version or later.
5. Is GHSA-MCMC-2M55-J8JJ exploitable, and should I be worried? Whether GHSA-MCMC-2M55-J8JJ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-MCMC-2M55-J8JJ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-MCMC-2M55-J8JJ? Upgrade vllm to 0.13.0 or later.

Other vulnerabilities in vllm