PoC Monitor
← All CVEs
CVE-2026-77359published 19 Nov 2026 17:03 UTCData: JSON · API

Datalayer jupyter-mcp-server

Jupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routes

Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode validates Host and Origin values for /mcp but does not apply the same browser-origin controls to the state-changing /api/connect and /api/stop management routes. A malicious website can use DNS rebinding so that its hostname resolves to a loopback, LAN, VPN, or published-container MCP listener, then send a browser-shaped request that /api/connect accepts to replace runtime_url and document_url values and start a kernel client against attacker-controlled infrastructure. The attacker can thereby cause Jupyter API and WebSocket traffic to reach that infrastructure and can use /api/stop to stop the current notebook kernel. The default broad bind can increase exposure, but the vulnerability is the missing management-route origin boundary, not a lack of Host validation on /mcp. This issue is fixed in version 1.0.3.

First public PoC 1.6 daysafter publication · 21 Nov 2026
Public PoCs11 on GitHub
CVSS9.3critical · scored by CNA · CWE-350
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

datalayer jupyter-mcp-server
  • < 1.0.3

Fixed in 1.0.3

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published19 Nov 2026 · t = 0First public PoC21 Nov 2026 · t+1.6d

First public PoC 1.6 days after publication; not in CISA KEV. First PoC: googlesky/CVE-2026-77359 (created 21 Nov 2026, found by us: 21 Nov 2026).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedFound by usStarsAssessment
googlesky/CVE-2026-77359 21 Nov 2026 +1.6 d 21 Nov 2026 0 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.