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

CVE-2026-77359

Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
GitHub, Inc. (opens in new tab)
Published
Last modified
NVD status
Received
CVSS 4.09.3Critical

Description

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.

Affected products

The products and versions with the vulnerability.

Listed by CNA

The products and versions affected, according to the organization that published this CVE.

VendorProductAffected versions
datalayerjupyter-mcp-server
  • < 1.0.3

Severity

How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).

  • 9.3 CriticalCVSS 4.0 · SecondaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by GitHub, Inc. (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Network
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    Attack requirementsWhether the attack depends on how the target is deployed or configured.
    None
    Privileges requiredThe access the attacker needs before attacking.
    None
    User interactionWhether someone other than the attacker has to do something, like open a link.
    None
    ConfidentialityHow much data the attacker can read.
    Low
    IntegrityHow much data the attacker can change.
    High
    AvailabilityHow much the attacker can disrupt the system or service.
    High
    Confidentiality, other systemsThe impact on other systems that depend on the vulnerable one.
    High
    Integrity, other systemsThe impact on other systems that depend on the vulnerable one.
    High
    Availability, other systemsThe impact on other systems that depend on the vulnerable one.
    High

    CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:HView in FIRST's calculator (opens in new tab)

Weaknesses and attack patterns

The type of bug behind the vulnerability, and how attackers exploit that type.

  • Reliance on Reverse DNS Resolution for a Security-Critical Action · CWE-350 (opens in new tab)

    The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.

    Abstraction
    Variant
    Mapping guidance
    Allowed

References

Advisories, patches, exploits and more about this vulnerability.

This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data