What happened
The v5.15.2 fix for GHSA-4pvg-m42h-c3x2 touched only McpSseServer; the Streamable HTTP handler in lib/mcp-transport-http.ts is unchanged since its introduction in v5.11.0, so the incomplete fix persists there. The proof of concept walks through a 0.0.0.0 bind reflecting the localhost Origin and returning the tool catalog with the header set.
Why it matters
This breaks an implicit trust invariant in an MCP transport on an externally-bound deployment: downstream code that assumes a reflected Access-Control-Allow-Origin means the Origin is trusted local is wrong, which can leak the tool surface of an AI agent's bridge to cross-origin callers.
Attack vector
McpStreamableServer reflects an Origin that is an http or https URL on localhost or 127.0.0.1 into Access-Control-Allow-Origin even when the server is bound to 0.0.0.0, granting a local web app, Electron window, or DNS-rebinding page readable cross-origin access to the unauthenticated GET /tools (full tool catalog) and GET /health routes. Tool invocation itself still requires the bearer token.
Affected systems
Jovancoding/Network-AI 5.11.0 to 5.17.1 (lib/mcp-transport-http.ts, McpStreamableServer)
Mitigation
Apply the same loopback-bind guard used for the SSE transport (isLoopbackHost) so Access-Control-Allow-Origin is only set when the server is actually bound to loopback; upgrade when a fix is published.