CVE-2026-111767

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

GHSA-22jm-h49p-29qw ↗EUVD-2026-105256 ↗

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.
npm:@modelcontextprotocol/sdk >= 1.24.0, < 1.32.0
fixed in 1.32.0
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-376, permanent identifier
pkg:npm/@modelcontextprotocol/sdk
1d 03h 05msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal −18dcve.org publicationwaiting for further signals+0.0d
−15d
−10d
−5d

description

@modelcontextprotocol/sdk 1.24.0 through 1.31.0 can expose experimental task records across sessions. A client may list, read, or cancel another session's tasks when the server supplies a shared InMemoryTaskStore through taskStore.

mitigation

Upgrade @modelcontextprotocol/sdk to version 1.32.0 or later. Until then, remove taskStore or use a distinct InMemoryTaskStore for each session.

fixed in 1.32.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.
contextual
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.35%26th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 18:28Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-02 20:54Z
  2. 2026-10-20 18:28Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-376",
  "cve_id": "CVE-2026-111767",
  "display_id": "CVE-2026-111767",
  "ghsa_id": "GHSA-22jm-h49p-29qw",
  "euvd_id": "EUVD-2026-105256",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-session task authorization flaw in @modelcontextprotocol/sdk",
  "summary": "@modelcontextprotocol/sdk 1.24.0 through 1.31.0 can expose experimental task records across sessions. A client may list, read, or cancel another session's tasks when the server supplies a shared InMemoryTaskStore through taskStore.",
  "mitigation": "Upgrade @modelcontextprotocol/sdk to version 1.32.0 or later. Until then, remove taskStore or use a distinct InMemoryTaskStore for each session.",
  "vendor": "npm",
  "product": "npm:@modelcontextprotocol/sdk",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.24.0, < 1.32.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.32.0"
      ],
      "package_name": "@modelcontextprotocol/sdk",
      "purl": "pkg:npm/@modelcontextprotocol/sdk"
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L",
  "epss_score": 0.0035,
  "epss_percentile": 0.2671,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.829788133333333,
  "t0_at": "2026-10-20T18:28:45.650000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T20:54:41+00:00",
      "days": -17.898664930555555,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T18:28:45.650000+00:00",
      "url": "https://github.com/modelcontextprotocol/typescript-sdk/security/advisories/GHSA-22jm-h49p-29qw"
    }
  }
}

published 2026-10-02 21:21Z
last change 2026-10-21 20:50Z

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.