CVE-2026-11719: CWE-862: Missing Authorization in Google MCP Toolbox for Databases (googleapis/mcp-toolbox)
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).
AI Analysis
Technical Summary
This vulnerability involves missing authorization checks in older protocol handlers of MCP Toolbox for Databases. While the newest protocol version enforces per-tool scope restrictions, older supported versions omit this enforcement. An authenticated client with limited privileges can bypass intended scope restrictions by using an older protocol version in the MCP-Protocol-Version header or by not specifying the header, which defaults to a vulnerable handler. This allows execution of high-privilege tools without proper authorization.
Potential Impact
An attacker with authenticated access and low-privilege tokens can escalate privileges by bypassing scope restrictions, potentially executing administrative or other high-privilege tools. This could lead to unauthorized actions within the MCP Toolbox for Databases environment. There are no known exploits in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should explicitly specify the protocol version header to use the 2025-11-25 handler that enforces scope restrictions. Monitor vendor advisories for updates or patches addressing this issue. Avoid relying on default protocol version handling until a fix is provided.
CVE-2026-11719: CWE-862: Missing Authorization in Google MCP Toolbox for Databases (googleapis/mcp-toolbox)
Description
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).
CVSS v4.0
Score 8.6high
Affected software
pkg:github/googleapis/mcp-toolboxRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability involves missing authorization checks in older protocol handlers of MCP Toolbox for Databases. While the newest protocol version enforces per-tool scope restrictions, older supported versions omit this enforcement. An authenticated client with limited privileges can bypass intended scope restrictions by using an older protocol version in the MCP-Protocol-Version header or by not specifying the header, which defaults to a vulnerable handler. This allows execution of high-privilege tools without proper authorization.
Potential Impact
An attacker with authenticated access and low-privilege tokens can escalate privileges by bypassing scope restrictions, potentially executing administrative or other high-privilege tools. This could lead to unauthorized actions within the MCP Toolbox for Databases environment. There are no known exploits in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should explicitly specify the protocol version header to use the 2025-11-25 handler that enforces scope restrictions. Monitor vendor advisories for updates or patches addressing this issue. Avoid relying on default protocol version handling until a fix is provided.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Date Reserved
- 2026-06-09T00:53:57.846Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a33df14f198dc38c1c0ed5d
Added to database: 06/18/2026, 12:05:40 UTC
Last enriched: 06/18/2026, 12:20:02 UTC
Last updated: 08/01/2026, 19:17:57 UTC
Views: 162
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.