vLLM· ()

This monthVendor security release

vLLM security release: 0.30.0

What
vLLM published security fixes. Upgrade to 0.30.0 (whichever matches your branch). Fixes 7 CVEs. Vendor severity: Medium.
Fix
Upgrade to 0.30.0
Why this tier
CVE-2026-105759: Public proof-of-concept exists (SSVC exploitation: poc).
Exploited
Not known to be exploited · highest EPSS 0.4%
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.30.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-105754 (and the other 6 CVEs):Debian · Ubuntu · Red Hat · Alpine

CVEs 7#

CVETierCVSSEPSSKEVSSVC exploitation
CVE-2026-105759This month5.9 (v3.1)0.4%Nopoc
CVE-2026-105754Routine6.5 (v3.1)0.3%Nonone
CVE-2026-105756Routine6.5 (v3.1)0.3%Nonone
CVE-2026-105757Routine6.5 (v3.1)0.3%Nonone
CVE-2026-105758Routine5.3 (v3.1)0.3%Nonone
CVE-2026-105760Routine5.3 (v3.1)0.3%Nonone
CVE-2026-105755Routine4.2 (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.