CVE•Published 2026-06-22•Modified 2026-06-24•0 articles on news•5 live references•NVD data
CVE-2026-54235Vllm · Vllm
Vulnerability data via NVD (ingested)
CVSS v3.1
6.5
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS percentile
23
Exploit Prediction Scoring System · top 77% of all CVEs
Weaknesses (CWE)
Description
vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, ll temperature validation gates use comparison operators (<, >), which silently evaluate to False for NaN and for positive Infinity in Python's IEEE 754 float semantics. Both values pass every guard and propagate to GPU sampling kernels, where they produce undefined behavior or CUDA errors that can crash the inference worker. This vulnerability is fixed in 0.23.1rc0.
Timeline
Published 2026-06-22
Modified 2026-06-24
External references
Search for exposed instances
Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).
Shodan · vuln tag0 hosts
vuln:CVE-2026-54235Hosts Shodan has explicitly fingerprinted as vulnerable.
Shodan · product
product:"Vllm Vllm"All exposed Vllm Vllm instances — cross-reference with the CVE's affected-version range.
Shodan · banner/body mention
http.html:"Vllm"HTTP body or banner mentions "Vllm" — catches deploys Shodan didn't identify as a product.
More intel sources (5)
Shodan report
vuln:CVE-2026-54235Country / ASN / product breakdown for the vuln query.
Censys
vulnerabilities.cve_id: CVE-2026-54235Censys host search filtered to this CVE id.
grep.app
CVE-2026-54235Public source-code mentions — fast PoC discovery.
GitHub code
CVE-2026-54235GitHub code search for direct mentions.
Google dork
"CVE-2026-54235" exploit -site:nvd.nist.govWrite-ups and news, NVD excluded.
Known PoCs on GitHub
No public proof-of-concept repositories found for CVE-2026-54235 on GitHub.
We haven't classified any articles referencing CVE-2026-54235 yet. The external references above still apply.