CVE-2026-103760

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

GHSA-mmqv-rpx9-mqhx ↗EUVD-2026-91134 ↗

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.
kvcache-ai Mooncake <= 0.3.13.post1
CWE-400 Uncontrolled Resource Consumption
ETK-2026-293, permanent identifier
19d 10h 09msince last run
1h 04mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h36m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Mooncake transfer engine through 0.3.13.post1 is affected by a denial-of-service issue in its handshake service. An unauthenticated attacker able to reach the handshake RPC port can prevent the service from handling subsequent handshake and related requests.

mitigation

Restrict access to the handshake RPC port to trusted hosts and networks until an upstream update is available. Limit or remove public exposure of affected Mooncake transfer-engine deployments.

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.40%32nd percentile
agent run time
1h 04m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 22:53Z
Δ 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-01 22:53Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-293",
  "cve_id": "CVE-2026-103760",
  "display_id": "CVE-2026-103760",
  "ghsa_id": "GHSA-mmqv-rpx9-mqhx",
  "euvd_id": "EUVD-2026-91134",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated handshake denial of service in Mooncake",
  "summary": "Mooncake transfer engine through 0.3.13.post1 is affected by a denial-of-service issue in its handshake service. An unauthenticated attacker able to reach the handshake RPC port can prevent the service from handling subsequent handshake and related requests.",
  "mitigation": "Restrict access to the handshake RPC port to trusted hosts and networks until an upstream update is available. Limit or remove public exposure of affected Mooncake transfer-engine deployments.",
  "vendor": "kvcache-ai",
  "product": "Mooncake",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.3.13.post1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Mooncake",
      "purl": null
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.004,
  "epss_percentile": 0.3288,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 63.5430767,
  "t0_at": "2026-10-01T22:53:05.201000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T22:53:05.201000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T22:53:05.201000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103760"
    }
  }
}

published 2026-10-02 02:25Z
last change 2026-10-21 10:52Z

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.