CVE-2026-107205

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

GHSA-87j8-jqhj-hfm7 ↗EUVD-2026-94384 ↗

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.
LMCache <= 0.5.5
CWE-306 Missing Authentication for Critical Function
ETK-2026-889, permanent identifier
14d 04h 30msince last run
48mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h45m
0
+4h
+6h
+8h
+10h
+12h

description

LMCache through 0.5.5 exposes its multiprocess coordinator HTTP fleet-control API without authentication. If that API is reachable, a remote attacker can alter instance and quota data, inject events, disrupt caching, and view placement metadata.

mitigation

Immediately restrict the coordinator HTTP API to trusted hosts or a private network and block untrusted access with network controls. Do not expose the API externally; apply a vendor release containing an authentication fix when one is published.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.39%32nd percentile
agent run time
48m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 15:24Z
Δ 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-07 15:24Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-889",
  "cve_id": "CVE-2026-107205",
  "display_id": "CVE-2026-107205",
  "ghsa_id": "GHSA-87j8-jqhj-hfm7",
  "euvd_id": "EUVD-2026-94384",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authentication in LMCache coordinator API",
  "summary": "LMCache through 0.5.5 exposes its multiprocess coordinator HTTP fleet-control API without authentication. If that API is reachable, a remote attacker can alter instance and quota data, inject events, disrupt caching, and view placement metadata.",
  "mitigation": "Immediately restrict the coordinator HTTP API to trusted hosts or a private network and block untrusted access with network controls. Do not expose the API externally; apply a vendor release containing an authentication fix when one is published.",
  "vendor": "LMCache",
  "product": "LMCache",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.5.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "LMCache",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0039,
  "epss_percentile": 0.3209,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 48.04836955,
  "t0_at": "2026-10-07T15:24:04.028000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T15:24:04.028000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T15:24:04.028000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107205"
    }
  }
}

published 2026-10-07 16:20Z
last change 2026-10-21 17:47Z

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.