Google MCP Toolbox for Databases 1.3.0 authorization

Summaryinfo

A vulnerability identified as critical has been detected in Google MCP Toolbox for Databases 1.3.0. This vulnerability affects unknown code. This manipulation causes authorization. The identification of this vulnerability is CVE-2026-11719. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in Google MCP Toolbox for Databases 1.3.0 and classified as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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).

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-11719 since 06/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/18/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-37881). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• Google

Name

• MCP Toolbox for Databases

Version

• 1.3.0

License

• free

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion