Jupyter MCP Server flaw lets unauthenticated callers redirect backend, fixed in 1.0.3
GitHub Advisory Database has published CVE-2026-77318 for the jupyter-mcp-server Python package. In standalone streamable-http mode, custom management routes skip the MCP token check, so unauthenticated network callers can change the Jupyter backend. Versions 1.0.2 and earlier are affected; 1.0.3 contains the fix.
The GitHub Advisory Database has published GHSA-24pw-rf5p-mgp7, tracked as CVE-2026-77318, against the jupyter-mcp-server package. According to the advisory, the /mcp endpoint requires a bearer token in standalone streamable-http mode, but custom management routes on the same application do not check that token. [1]
The advisory says an unauthenticated network caller can send a PUT request to /api/connect to set the Jupyter backend URL and tokens, reset the server context, and start a kernel client against infrastructure the attacker controls. It also says the DELETE /api/stop route lacks the same check and can remove the current notebook from the server. [1]
The advisory includes a reproduction on a specific project commit. It reports that the protected /mcp endpoint returned 401 without credentials, while the unauthenticated /api/connect request returned 200 with a success response. TechDots has not independently reproduced this result. [1]
GitHub rates the issue high severity. The advisory lists affected versions as 1.0.2 and earlier, with 1.0.3 as the fixed release. The material TechDots received gives no numeric score and does not state whether the flaw has been exploited in the wild. [1]
What we couldn't confirm
- No independent confirmation of the flaw beyond the advisory's own reproduction.
- No named source states exploitation status, and no in-the-wild evidence was reviewed.
- No numeric CVSS score was provided in the source material.
- The number of publicly reachable vulnerable instances is unknown.
- The source does not say whether the reproduction was run by maintainers or an outside researcher.
- No statement from the jupyter-mcp-server maintainers on the fix or disclosure timeline was provided.
Sources
- GitHub Advisory Database: GHSA-24pw-rf5p-mgp7 (CVE-2026-77318): Jupyter MCP Server: Unauthenticated management routes can hijack the Jupyter backend in standalone HTTP modeSource published · TechDots found it
Statements labelled as a company's claim have not been independently confirmed by TechDots.
Get Cybersecurity stories by email
Related coverage
nginx2root: five new nginx bugs, patch now and lock origins to Cloudflare
F5 and nginx.org disclosed ten nginx vulnerabilities on November 18, 2026. Five memory corruption flaws, named nginx2root by Xint, can crash workers or run commands, and one HTTP/2 bug is the most widespread. Cloudflare says its edge is unaffected and that its proxy shields origins from the HTTP/2 and HTTP/3 attacks, but patching is still required.
Etherpad pre-auth file read flaw rated critical in GitHub advisory
GitHub Advisory Database has published an advisory for an unauthenticated file-read flaw in Etherpad's /static/* handler, affecting ep_etherpad-lite versions 1.8.14 up to 3.3.3 and fixed in 3.3.3. The advisory rates it critical, CVSS 9.8.