Is CVE-2026-11719 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-11719 being exploited in the wild.

How severe is CVE-2026-11719?

High severity, with a CVSS score of 4, published 18 June 2026.

Which products and versions are affected?

github.com/googleapis/mcp-toolbox (Go) < 1.4.0, SEMVER:introduced=0,fixed=1.4.0; Google MCP Toolbox for Databases < 1.4.0, 1.3.0.

Is there a fix for CVE-2026-11719?

Yes. github.com/googleapis/mcp-toolbox (Go): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-11719 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-11719?

Check whether you run github.com/googleapis/mcp-toolbox (Go) or Google MCP Toolbox for Databases at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-11719: Google MCP Toolbox for Databases authorization bypass in protocol handlers

Q: Is there a fix for CVE-2026-11719?

Yes. github.com/googleapis/mcp-toolbox (Go): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-11719 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-11719?

Check whether you run github.com/googleapis/mcp-toolbox (Go) or Google MCP Toolbox for Databases at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-11719 · Severity: high · CVSS 4 · Published 2026-06-18

Google MCP Toolbox for Databases, a tool used to manage database interactions, contains a security flaw that allows users with limited access to perform unauthorized administrative actions. By manipulating the protocol version used in their requests, an authenticated user can bypass security checks that were only implemented in newer versions of the software. This could lead to unauthorized data access or the execution of high-privilege administrative commands.

Technologies: github.com/googleapis/mcp-toolbox (Go), Google MCP Toolbox for Databases. Vendors: Go, Google.

Quick answers

Is CVE-2026-11719 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-11719 being exploited in the wild.
How severe is CVE-2026-11719?: High severity, with a CVSS score of 4, published 18 June 2026.
Which products and versions are affected?: github.com/googleapis/mcp-toolbox (Go) < 1.4.0, SEMVER:introduced=0,fixed=1.4.0; Google MCP Toolbox for Databases < 1.4.0, 1.3.0.
Is there a fix for CVE-2026-11719?: Yes. github.com/googleapis/mcp-toolbox (Go): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-11719 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-11719?: Check whether you run github.com/googleapis/mcp-toolbox (Go) or Google MCP Toolbox for Databases at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/googleapis/mcp-toolbox (Go): upgrade to 1.4.0 or later
```
go get github.com/googleapis/mcp-toolbox@v1.4.0
```

Technical details

An authenticated authorization bypass exists in MCP Toolbox for Databases due to inconsistent scope enforcement across Model Context Protocol (MCP) handlers. While the 2025-11-25 protocol version correctly validates 'scopesRequired' for tool execution, older supported versions (2025-06-18, 2025-03-26, and 2024-11-05) omit these checks. A remote attacker with a valid low-privilege token (e.g., read-only) can bypass intended restrictions by setting the 'MCP-Protocol-Version' header to a vulnerable version or omitting it to trigger the default 2024-11-05 handler. This allows the execution of administrative tools. The issue was addressed by centralizing scope validation logic across all protocol versions.

Affected products

Google MCP Toolbox for Databases (googleapis/mcp-toolbox) 1.3.0

Identifiers

CVE-2026-11719
GHSA-5gf6-gc35-xjpc
GO-2026-5144

Timeline

2026-05-13: other: Initial tool-level scope validation implemented in version 2025-11-25
2026-06-03: patched: Fix merged to centralize validation across all protocol versions
2026-06-18: disclosed
2026-06-18: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.