CVE-2026-105756

waiting for further signalsZero needs more public information before it can validate it.

GHSA-2823-qmq8-rwvj ↗EUVD-2026-92846 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
vllm-project vllm < 0.30.0
fixed in >= 30.0.0
CWE-20 Improper Input Validation, CWE-248 Uncaught Exception
ETK-2026-1333Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/vllm
20h 39msince last run
1h 31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+346h18m
0
+2h
+4h
+6h
+8h
+10h

description

pip vllm releases before 30.0.0 can mishandle client-provided cache salt values. A requester able to reach the service can disrupt the engine and concurrent workloads when the LMCache-MP KV connector is enabled.

mitigation

Upgrade vllm to >= 30.0.0 or later.

fixed in >= 30.0.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%22nd percentile
agent run time
1h 31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 22:49Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-05 22:49Z
  2. 2026-10-05 22:49Z
  3. 2026-10-07 15:34Z
    Unpatched Critical LMCache Flaw Lets Unauthenticated Attackers Run Code Remotely

this entry in the feed

GET /api/v1/feed/CVE-2026-105756

{
  "etk_id": "ETK-2026-1333",
  "cve_id": "CVE-2026-105756",
  "display_id": "CVE-2026-105756",
  "ghsa_id": "GHSA-2823-qmq8-rwvj",
  "euvd_id": "EUVD-2026-92846",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cache salt validation denial of service in pip vllm",
  "summary": "pip vllm releases before 30.0.0 can mishandle client-provided cache salt values. A requester able to reach the service can disrupt the engine and concurrent workloads when the LMCache-MP KV connector is enabled.",
  "mitigation": "Upgrade vllm to >= 30.0.0 or later.",
  "vendor": "vllm-project",
  "product": "vllm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.30.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        ">= 30.0.0"
      ],
      "package_name": "vllm",
      "purl": "pkg:pypi/vllm"
    }
  ],
  "cwes": [
    20,
    248
  ],
  "cvss_score": 6.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0031,
  "epss_percentile": 0.2287,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 91.07821601666667,
  "t0_at": "2026-10-05T22:49:59.642000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T22:49:59.642000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T22:49:59.642000+00:00",
      "url": "https://thehackernews.com/2026/10/unpatched-critical-lmcache-flaw-lets.html"
    }
  }
}

published 2026-10-12 08:39Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.