Skip to main content
No exploitation reportedFix available

CVE-2025-62164

No exploitation reported by the sources we read.

  • Published2025-11-21
  • Fixed in0.11.1
  • WeaknessCWE-123 · CWE-20 · CWE-502

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

vLLM is an inference and serving engine for large language models (LLMs). From versions 0.10.2 to before 0.11.1, a memory corruption vulnerability could lead to a crash (denial-of-service) and potentially remote code execution (RCE), exists in the Completions API endpoint. When processing user-supplied prompt embeddings, the endpoint loads serialized tensors using torch.load() without sufficient validation. Due to a change introduced in PyTorch 2.8.0, sparse tensor integrity checks are disabled by default. As a result, maliciously crafted tensors can bypass internal bounds checks and trigger an out-of-bounds memory write during the call to to_dense(). This memory corruption can crash vLLM and potentially lead to code execution on the server hosting vLLM. This issue has been patched in version 0.11.1.

Timeline

dates in UTC
  1. 2025-11-2102:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-62164?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-62164?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Vllm
BranchAffectedFixed in
0.x≥ 0.10.2, < 0.11.10.11.1
0.11= 0.11.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • RHSA-2026:19712 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: RHOAI 3.3.3 - Red Hat OpenShift AI

  • RHSA-2026:3713 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: RHOAI 3.3 - Red Hat OpenShift AI

  • RHSA-2026:3462 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (ROCm)

  • RHSA-2026:3461 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (CUDA)

  • RHSA-2025:23449 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat AI Inference Server 3.2.5 (ROCm)

  • RHSA-2025:23209 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat AI Inference Server 3.2.5 (TPU)

2 more advisories

Full record on NVD

Fix

  1. Update Vllm to 0.11.1
  2. Vendor fix Red Hat Product Security RHSA-2026:19712 · 2 productsFor Red Hat OpenShift AI 3.3.3 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
  3. Vendor fix Red Hat Product Security RHSA-2026:3713 · 1 productFor Red Hat OpenShift AI 3.3 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/
  4. Vendor fix Red Hat Product Security RHSA-2026:3462 · 1 productFor more information visit https://access.redhat.com/errata/RHSA-2026:3462
  5. Vendor fix Red Hat Product Security RHSA-2026:3461 · 2 productsFor more information visit https://access.redhat.com/errata/RHSA-2026:3461
  6. Vendor fix Red Hat Product Security RHSA-2025:23449 · 1 productFor more information visit https://access.redhat.com/errata/RHSA-2025:23449
  7. Vendor fix Red Hat Product Security RHSA-2025:23209 · 1 productFor more information visit https://access.redhat.com/errata/RHSA-2025:23209

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2025-11-24
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.18.8read 2026-10-23
  • CNAweakness (CWE)CWE-123, CWE-20, CWE-502, CWE-787read 2026-10-23
  • FIRST EPSSEPSS score1.0 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2025-11-21
Last Modified
2026-10-19
NVD status
Analyzed

Frequently asked questions

What is CVE-2025-62164?

vLLM is an inference and serving engine for large language models (LLMs). From versions 0.10.2 to before 0.11.1, a memory corruption vulnerability could lead to a crash (denial-of-service) and potentially remote code execution (RCE), exists in the Completions API endpoint. When processing user-supplied prompt embeddings, the endpoint loads serialized tensors using torch.load() without sufficient validation. Due to a change introduced in PyTorch 2.8.0, sparse tensor integrity checks are disabled by default. As a result, maliciously crafted tensors can bypass internal bounds checks and trigger an out-of-bounds memory write during the call to to_dense(). This memory corruption can crash vLLM and potentially lead to code execution on the server hosting vLLM. This issue has been patched in version 0.11.1.

Is CVE-2025-62164 actively exploited?

Active exploitation of CVE-2025-62164 has not been confirmed. Its EPSS score was 1.0% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-62164?

CVE-2025-62164 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running vllm? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database