CVE-2026-77318: Jupyter MCP Server: Unauthenticated management routes can hijack the Jupyter backend in standalone HTTP mode
Standalone streamable-http mode in datalayer/jupyter-mcp-server requires MCP_TOKEN for /mcp, but the custom management routes mounted on the same application do not enforce that token. An unauthenticated network caller can invoke PUT /api/connect, choose the Jupyter backend URL and token fields, reset the server context, and make the MCP server start a kernel client against attacker-controlled infrastructure. The same missing authentication affects the state-changing DELETE /api/stop route.
The intended authentication boundary is documented in the security guide and enforced during startup:
docs/docs/reference/security/index.mdx:15
All MCP endpoints require Bearer token authentication.
docs/docs/reference/security/index.mdx:25
Starting with version 1.0.0, MCP client authentication is required for the streamable-http transport.
The CLI enforces that boundary for the MCP endpoint:
References
- github.com/advisories/GHSA-24pw-rf5p-mgp7
- github.com/datalayer/jupyter-mcp-server/commit/c2e98fca2df1bbd608451ec416aaa38a4d246fc5
- github.com/datalayer/jupyter-mcp-server/pull/262
- github.com/datalayer/jupyter-mcp-server/releases/tag/v1.0.3
- github.com/datalayer/jupyter-mcp-server/security/advisories/GHSA-24pw-rf5p-mgp7
- nvd.nist.gov/vuln/detail/CVE-2026-77318
Code Behaviors & Features
Detect and mitigate CVE-2026-77318 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →