Unauthenticated tool invocation via legacy API
Published Jul 31, 2026 · Updated Jul 31, 2026
Incorrect authorization in Google MCP Toolbox for Databases 1.3.0 and 1.4.0 allows remote attackers to invoke scope-protected tools. The legacy HTTP tool invocation route bypasses MCP authorization middleware and dispatches requests without evaluating scopesRequired. Exposure requires MCP authorization to be configured and the non-default --enable-api flag to be active; resulting access is bounded by the configured tools.
Summary
What happened
Incorrect authorization in Google MCP Toolbox for Databases 1.3.0 and 1.4.0 allows remote attackers to invoke scope-protected tools. The legacy HTTP tool invocation route bypasses MCP authorization middleware and dispatches requests without evaluating scopesRequired. Exposure requires MCP authorization to be configured and the non-default --enable-api flag to be active; resulting access is bounded by the configured tools.
The record
- CVE
- CVE-2026-14537
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- Go standard library
- Product
- MCP Toolbox for Databases
- Classifications
- CWE-863, CAPEC-180, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.3.0
- Affected versionversion=v1.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo