Skip to main content
VulnerabilityPublished

CVE-2026-77318: datalayer jupyter-mcp-server · Missing Authentication for Critical Functionality

Affects datalayer jupyter-mcp-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.3 High : upgrade to 1.0.3 soon.

Data as of 19 Nov 2026, 17:21 UTC

CVSS 4.0 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.07.3
Patch
Available – fixed in 1.0.3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:H/SI:H/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade datalayer jupyter-mcp-server to 1.0.3.

Affected software

ProductAffectedFixed in
datalayerjupyter-mcp-serverAffected
  • <1.0.3
Fixed in
  • 1.0.3

AI-suggested

Upgrade jupyter-mcp-server to version 1.0.3 or later, where this authentication issue is fixed. No other mitigation is required as the fix addresses the root cause.

Description

Jupyter MCP Server versions prior to 1.0.3 have a missing authentication vulnerability in standalone streamable-http mode. The /api/connect and /api/stop management routes are unauthenticated, allowing an attacker to manipulate runtime and document URLs, reset server context, start kernel clients against attacker-controlled infrastructure, and stop notebook kernels. This flaw is fixed in version 1.0.3.

References

Community reviews

Loading reviews…