vLLM makes Use of Uninitialized Resource

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.9 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2026-7141: 0.29% estimated exploitation activity in the next 30 days; percentile 21.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability was found in vLLM up to 0.19.0. The affected element is the function hasmambalayers of the file vllm/v1/kvcacheinterface.py of the component KV Block Handler. Performing a manipulation results in uninitialized resource. It is possible to initiate the attack remotely. The attack is considered to have high complexity. The exploitability is described as difficult. The exploit has been made public and could be used. The patch is named 1ad67864c0c20f167929e64c875f5c28e1aad9fd. To fix this issue, it is recommended to deploy a patch.

Published by the source

27 Apr 2026, 18:32 UTC

Last modified by the source

10 Sep 2026, 03:51 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x368-4g9h-fvv4

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x368-4g9h-fvv4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-7141

Advisory: vLLM makes Use of Uninitialized Resource
IDs: CVE-2026-7141, GHSA-x368-4g9h-fvv4
Record: https://patchnext.com/advisories/cve-2026-7141 (revision 3, source checked 26 Oct 2026, 13:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vllm 0.19.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI vllm: affected < 0.19.1; fixed in 0.19.1

## Suggested inspection (read-only)
- `python -m pip show vllm`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on vllm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x368-4g9h-fvv4 (OSV record GHSA-x368-4g9h-fvv4 lists affected ranges: PyPI vllm >=0 <0.19.1 (fixed))
- Verified: https://github.com/advisories/GHSA-x368-4g9h-fvv4 (GitHub-reviewed advisory GHSA-x368-4g9h-fvv4 lists affected ranges: PyPI vllm >=0 <0.19.1)

Commands are suggestions: review each one before running it.