What happened
The standalone streamable-HTTP app validates Host and Origin on /mcp but not on the management routes. The fix adds MANAGEMENT_ROUTE_PATHS and AUTHENTICATED_MANAGEMENT_ROUTE_PATHS and a ManagementRouteSecurityMiddleware that rejects non-loopback Host headers, non-local Origins, and (when a token verifier is set) unauthenticated calls to /api/connect and /api/stop. CVE-2026-77318 (CVSS 7.3) is the closely related unauthenticated-management-route defect fixed in the same commit.
Why it matters
Jupyter is a core data-science/ML environment that agents frequently drive as a tool. An unauthenticated or browser-origin attacker could take over or kill the agent's compute session, disrupting RAG/inference workflows and enabling cross-application access within the Jupyter trust boundary.
Attack vector
The state-changing /api/connect and /api/stop management routes are not covered by the Host/Origin validation or MCP_TOKEN auth applied to /mcp, so a malicious web page can issue cross-origin requests to connect to or tear down the Jupyter kernel an agent uses.
Affected systems
datalayer/jupyter-mcp-server below 1.0.3 (standalone streamable-HTTP mode)
Mitigation
Upgrade to jupyter-mcp-server 1.0.3 or later, which adds ManagementRouteSecurityMiddleware enforcing local-Host/Origin validation and bearer auth on /api/connect and /api/stop.