vLLM· ()

This monthVendor security release

vLLM security release: 0.32.0

What
vLLM published security fixes. Upgrade to 0.32.0 (whichever matches your branch). Fixes 9 CVEs. Vendor severity: Low, Medium, High.
Fix
Upgrade to 0.32.0
Why this tier
Vendor security release for server software (most severe: CVE-2026-94624).
Exploited
Not known to be exploited · highest EPSS 0.7%
Share this

What to do now#

  1. Check whether you run an affected vLLM version:
    pip show vllm | grep Version
  2. Upgrade to the fixed release for your branch: 0.32.0.Vendor announcement
  3. Pull the fixed vllm/vllm-openai image or pip install -U vllm, then restart the server. Never expose the API without auth.
  4. Using distro packages? Distros backport fixes under their own version numbers. Check your distro's status for CVE-2026-115911 (and the other 8 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 9#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-94624Routine8.7 (v4.0)0.4%Nonone
CVE-2026-115915Routine8.1 (v3.1)0.7%Nonone
CVE-2026-115912Routine7.5 (v3.1)0.5%Nonone
CVE-2026-115911Routine6.5 (v3.1)0.3%Nonone
CVE-2026-115913Routine6.5 (v3.1)0.3%Nonone
CVE-2026-115914Routine6.5 (v3.1)0.4%Nonone
CVE-2026-115916Routine6.5 (v3.1)0.3%Nonone
CVE-2026-115918Routine6.5 (v3.1)0.4%Nonone
CVE-2026-115917Routine3.4 (v3.1)0.2%Nonone

Sources#

Built from vLLM: GitHub Security Advisories (vllm-project/vllm), checked . Tier from the published rubric.

Also on today's list

See today's list → · Coming up →

Something wrong on this page?
Anonymous. Reports are checked against the primary source.