AAK-MCP-HTTP-NOAUTH-SERVER-001: Published MCP HTTP/SSE server exposes an unauthenticated network-bound endpoint
- Severity
- HIGH
- Category
- MCP Configuration (
mcp-config) - Scanner
agent_audit_kit/scanners/mcp_http_noauth_server.py- Auto-fixable
- No.
- SARIF name
McpHttpServerNoAuth
What it detects
A repository publishes an MCP server over HTTP / SSE / Streamable-HTTP (an /mcp route handler, or an SSEServerTransport / StreamableHTTPServerTransport / --http setup) with no inbound authentication marker on the handler, while also binding to all interfaces (0.0.0.0 / ::) or serving a wildcard Access-Control-Allow-Origin: *. The result is a mutation-capable RPC endpoint, backed by the operator's own tokens, reachable without credentials by any network (or, with wildcard CORS, any cross-origin browser) peer. This is a recurring 2026 class: GitLab MCP Server (CVE-2026-44895), Nocturne Memory (CVE-2026-44830), and AgenticMail (CVE-2026-50287) all shipped auth-less HTTP/SSE MCP transports on 0.0.0.0 with wildcard CORS. Generalises the Azure-only AAK-AZURE-MCP-NOAUTH-001 to any published MCP HTTP server (the Azure rule still owns Azure-MCP repos; this rule defers to it there). Beyond server source, this also flags the launch surface: MCP config files (mcp.json, claude_desktop_config.json, *.mcp.yaml command/args), Docker --host 0.0.0.0 / -p 0.0.0.0: publishes, and MCP Inspector / FastMCP startup args that bind a non-loopback interface (0.0.0.0 / :: / a routable IP) with no token / requireAuth, or with the Inspector kill-switch DANGEROUSLY_OMIT_AUTH set. CVE-2026-23744 (MCP Inspector, CVSS 9.8) is the motivating exemplar of the launch-bind variant; Censys counted ~12,520 MCP services exposed on the public internet in this shape. Two further 2026 instances of this exact class: CVE-2026-49257 (mcp-pinot <= 3.0.1, CVSS 10.0) defaults to an HTTP MCP server bound to 0.0.0.0:8080 with no authentication, exposing SQL execution as a confused deputy; CVE-2026-48989 (Windows-MCP < 0.7.5, CVSS 8.9) exposed the MCP control plane over HTTP without auth while enabling wildcard CORS. CWE-306 (Missing Authentication for Critical Function).
How to fix
Require an inbound credential on every /mcp route / SSE handler (bearer/JWT/mTLS/API-key middleware) and fail closed when the credential is unset — never bypass auth when an API_TOKEN env var is empty. Bind the listener to 127.0.0.1 (or behind an authenticating reverse proxy) instead of 0.0.0.0, never pass --host 0.0.0.0 to the MCP Inspector / FastMCP without a token, never set DANGEROUSLY_OMIT_AUTH, and replace wildcard CORS with an explicit origin allowlist (see AAK's wildcard-CORS rule).
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-HTTP-NOAUTH-SERVER-001
Limitations
Source files are checked for a literal 0.0.0.0 or :: bind or a wildcard CORS setting, so a Node server that calls listen(3000) with no host, which binds every interface, is not treated as exposed. In compose, Dockerfile and JSON or YAML launch files, any api_key, bearer, Authorization or --token text counts as inbound authentication, including the server's own outbound OPENAI_API_KEY.
References
- CVE: CVE-2026-44895, CVE-2026-44830, CVE-2026-50287, CVE-2026-23744, CVE-2026-49257, CVE-2026-48989, CVE-2026-90617, CVE-2026-38924, CVE-2026-59971, CVE-2026-53710, CVE-2026-57139, CVE-2026-61560, CVE-2026-54618, CVE-2026-54504, CVE-2026-58197, CVE-2026-54446, CVE-2026-77244, CVE-2026-77254
- OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization)
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse)
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-HTTP-NOAUTH-SERVER-001.md: the page then shows that text, with the registry reference appended under it.