CVE-2026-11719: MCP Toolbox for Databases: authenticated authorization bypass
MCP Toolbox for Databases before 1.4.0 enforces per-tool `scopesRequired` only in its 2025-11-25 protocol handler. An authenticated client with a low-privilege token, such as `read`, can call admin-level tools by sending an older `MCP-Protocol-Version` header or none at all. Upgrade to github.com/googleapis/mcp-toolbox 1.4.0.
Published Jun 18, 2026 · Updated Jun 19, 2026 · Analysis Nov 1, 2026
What an attacker can do
Toolbox lets you attach scopesRequired to a tool, so only tokens carrying those scopes may call it. The handler for protocol version 2025-11-25 checks this. The handlers for 2025-06-18, 2025-03-26 and 2024-11-05 do not. The server picks the handler from the MCP-Protocol-Version request header. When the header is missing, it falls back to the 2024-11-05 handler, which has no scope check.
So the bypass needs no trick beyond choosing an old version or dropping the header. A client that holds any valid token, even one limited to read, can then run tools you marked as admin. Those tools act on the databases wired to Toolbox, so the result is reading or changing data the token was never meant to reach (CWE-862).
The attacker needs a valid account and token, which is why the vector shows low privileges, but no user interaction. Deployments that rely on scopes to separate read-only agents from administrative ones are the ones that lose that boundary. Deployments that do not use scopesRequired see no change.
Who is affected
Affected: github.com/googleapis/mcp-toolbox below 1.4.0, where tools define scopesRequired and the server accepts the older protocol versions 2025-06-18, 2025-03-26 and 2024-11-05. Without scope restrictions on tools there is nothing to bypass.
toolbox --versionFor a Go module dependency:
go list -m github.com/googleapis/mcp-toolboxThen look in your tools configuration for scopesRequired.
github.com/googleapis/mcp-toolbox
- Ecosystem
- Go
- Affected
- < 1.4.0
- Fixed in
- 1.4.0
- Check
go list -m github.com/googleapis/mcp-toolbox
How to fix it
Upgrade to github.com/googleapis/mcp-toolbox 1.4.0:
go get github.com/googleapis/[email protected]For the prebuilt binary or container, pull the 1.4.0 release. The references point to pull requests 3049 and 3335 for the change. The sources name no workaround. Until you can upgrade, issue tokens with only the scopes each client needs, and do not rely on scopesRequired as the only barrier to administrative tools. Use database-side permissions for the credentials Toolbox connects with.
How to tell if you were hit
Look in Toolbox request logs for calls with no MCP-Protocol-Version header, or with 2024-11-05, 2025-03-26 or 2025-06-18, that invoke tools having scopesRequired. Match each call to the scopes on the token. A read token invoking an admin tool is the signal.
On the database side, review audit logs for administrative statements run by the Toolbox service account that do not match any known admin session.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
An authenticated authorization bypass vulnerability exists in MCP Toolbox for Databases due to missing scope enforcement across older protocol handlers.
While the 2025-11-25 protocol version handler correctly enforces per-tool restrictions defined by scopesRequired, older supported protocol versions (2025-06-18, 2025-03-26, and 2024-11-05) omit this check. An authenticated client with low-privilege tokens (e.g., read) can bypass the intended per-tool scope restrictions and execute high-privilege tools (e.g., admin) simply by specifying an older protocol version in the MCP-Protocol-Version header, or by omitting the header entirely (which causes the server to default to the vulnerable 2024-11-05 handler).
Questions
- Which version fixes CVE-2026-11719?
mcp-toolbox 1.4.0. Earlier releases enforce
scopesRequiredonly in the 2025-11-25 protocol handler.- What does the attacker need?
A valid low-privilege token and network access to Toolbox. They then send an older
MCP-Protocol-Versionvalue, or omit the header, to reach the handlers that skip scope checks.- Why does omitting the header work?
Without the header, the server defaults to the 2024-11-05 handler, which does not enforce
scopesRequired.- Is it exploited in the wild?
No source reports exploitation, and it is not in CISA's KEV catalog.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Other MCP servers and tools vulnerabilities
All Other MCP servers and tools entriesCVE-2026-102943
Dagu MCP DAG specification read bypasses path containment and workspace isolation
medium6.5Nov 10, 2026CVE-2026-102610
fast-agent: `fast-agent serve` binds HTTP to 0.0.0.0 with no authentication by default; with --shell this is unauthenticated remote command execution
medium6.4Nov 9, 2026CVE-2026-63655
tsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS
high7.5Nov 9, 2026CVE-2026-76892
tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process
high8.7Nov 9, 2026CVE-2026-76893
tsParticles: A single anonymous MCP session can monopolize HTTP mode and deny new clients
medium6.9Nov 9, 2026CVE-2026-77604
Code Graph RAG: MCP paginated read_file path traversal / arbitrary file read
high7.5Nov 9, 2026
