CVE-2026-93592Disclosure(vllm / vllm)

LOWCVSS 8.7 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch vllm vllm systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

vLLM versions before 0.28.0 fail to validate the lower bound of token IDs in the /v1/embeddings and /pooling endpoints, allowing unauthenticated attackers to crash the engine by submitting negative token IDs. A single request with a negative token ID triggers a CUDA device-side assertion that poisons the GPU context, causing all subsequent requests to fail until the process restarts.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-129

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • vllm

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 2 signals
  • Disclosure: 1 classified signal
  • Peaked 1d ago at 1 mentions (2026-09-19); latest day: 1
  • 2 total mentions across 2 days

Affected systems

Vendors
Products
vllm

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-09-19: 1Mentions · 2026-09-22: 1Patch / Workaround · 2026-09-22: 1Technical Details · 2026-09-19: 1Technical Details · 2026-09-22: 109-1909-22
Signal classification2 categories
Disclosure
150.0%
Patch
150.0%
Referenced assets1 URL
Classification over time
DateTotalLabels
2026-09-191
Disclosure1
2026-09-221
Patch1
Full discourse2 posts
  • Upwind Security MDR@UpwindMDR
    Patch

    🚨HIGH - vLLM DoS via Negative Token IDs in Embeddings/Pooling (CVE-2026-93592) vLLM’s OpenAI-compatible API /v1/embeddings and /pooling fail to validate the lower bound of token IDs; unauthenticated attackers can submit negative IDs to hit a CUDA device-side assert, crashing/poisoning the GPU context. Subsequent requests fail until the process restarts. 👉Affected: vllm < 0.28.0 | Upgrade to 0.28.0

    Post summary

    The tweet discloses a denial‑of‑service vulnerability in vLLM (CVE‑2026‑93592) affecting versions <0.28.0 and recommends upgrading to 0.28.0 to mitigate the issue.

    10020110
    321 followersView on X
  • NewNormal Security@NewScanTeam
    Disclosure

    NewNormal Security turns CVEs since the previous batch into new detections, every day. 𝗗𝗮𝗶𝗹𝘆 𝗖𝗩𝗘 𝗥𝗲𝗽𝗼𝗿𝘁 — 19 Sep 2026 𝗔𝗱𝗱𝗲𝗱 to NewScan 𝘁𝗼𝗱𝗮𝘆: 🖥️ Container registry open to anonymous push, or running a build whose bearer-token check can be bypassed — every image, and a tag they can overwrite (zot CVE-2026-61833) 🖥️ Database console on the internet — a login in front of a database whose permission checks any account can walk around (ArcadeDB CVE-2026-93593, CVE-2026-93594, CVE-2026-93595, CVE-2026-93598) 🖥️ Self-hosted AI model server with no authentication — free inference on your GPUs, and one bad request stops the engine for everyone (as seen in vLLM CVE-2026-93592) Test your stack with NewScan — free, self-hosted: https://newnormalsecurity.com/newscan?utm_source=x&utm_medium=social&utm_campaign=daily-cve #infosec #AppSec #ExposedInterface #CSO #REDTEAM

    Post summary

    The post discloses multiple newly detected CVEs affecting container registries, databases, and AI model servers, providing technical descriptions of each vulnerability but without mentioning patches, exploits, or active exploitation.

    0001066
    7 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appvllmvllm---

Explore more