Skip to content

1.0.119

Choose a tag to compare

View all tags
@nictuku nictuku released this 30 Jul 17:23
· 11 commits to main since this release
1.0.119
ef2592d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Security

GHSA-8353-5qhw-8hfw — Unauthenticated HTTP MCP tool execution under --sse-response (Critical, CVSS 9.1)

Under --transport streamable-http --sse-response, the HTTP auth middleware was attached to a Starlette app that was not the one actually served, so the served endpoint carried no auth gate. Requests could reach tool handlers and fall back to the operator's META_ACCESS_TOKEN.

  • Affected: <= 1.0.118, only when run with --sse-response and a META_ACCESS_TOKEN env var on a network-reachable interface. The default JSON response mode is not affected. The hosted MCP at *.mcp.pipeboard.co was not affected.
  • Fixed in: 1.0.119 — the auth middleware is now attached to the served app unconditionally (independent of the response-format setting), with the SSE app covered as well for defense-in-depth. Regression tests assert the served app rejects unauthenticated requests in both JSON and --sse-response modes.
  • Operator action: upgrade to 1.0.119. If you ran an affected configuration, rotate the Meta access token and review Graph API access logs.

See SECURITY.md for the full advisory and STREAMABLE_HTTP_SETUP.md for the documented HTTP per-request auth model.

Full Changelog: 1.0.118...1.0.119

Assets 2
Loading