Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-14537 – Authorization Bypass – Google MCP Toolbox for Databases v1.3.0 and v1.4.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-14537 is an Incorrect Authorization vulnerability (CWE-863) in Google MCP Toolbox for Databases versions v1.3.0 and v1.4.0. An unauthenticated remote attacker can invoke tools protected by the scopeRequired authorization feature by routing tool invocation requests through legacy HTTP endpoints when the --enable-api flag is active, completely bypassing the intended access controls. With a CVSS 4.0 score of 8.1 (High) and high impact on confidentiality, integrity, and availability, this flaw poses a direct risk to any database system connected to an exposed toolbox instance.

Technical details

  • Root cause: When both MCP Authorization (scopeRequired) and the legacy HTTP API (--enable-api) are enabled simultaneously, the legacy endpoints do not enforce per-tool scope restrictions. The authorization logic governing which callers may invoke which tools is applied only to the modern MCP protocol handlers; the legacy HTTP invocation path omits these checks entirely, creating a bypass path.
  • Trigger conditions: The vulnerability is exploitable only when the --enable-api flag is active and scopeRequired has been configured on one or more tools. Both conditions must be present.
  • Attack vector: Network — fully remote and unauthenticated. No credentials, no user interaction, and no prior foothold are required. An attacker sends tool invocation requests directly to the exposed legacy HTTP endpoint.
  • Impact: Successful exploitation allows an unauthenticated attacker to invoke database-connected tools that are intended to be restricted by scope. Depending on the tools configured, this may enable unauthorized querying, modification, or deletion of data in connected databases, with high impact on confidentiality, integrity, and availability.

Affected software

  • Google MCP Toolbox for Databases v1.3.0
  • Google MCP Toolbox for Databases v1.4.0

Severity

CVSS 4.0 Base Score: 8.1 (High)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

Mitigation and recommended actions

  • Immediate — upgrade: Update to Google MCP Toolbox for Databases v1.5.0 or later. Version 1.5.0 (released June 18, 2026) introduces a startup validation check that enforces mutual exclusivity between MCP Authorization and the legacy HTTP API, preventing the server from starting in an insecure configuration.
  • Workaround (if immediate upgrade is not possible): Disable the --enable-api flag to eliminate the vulnerable legacy HTTP endpoint. If the flag cannot be disabled, remove scopeRequired scope restrictions from all tools and enforce access control at the network perimeter (e.g., firewall rules, reverse proxy authentication) until patching is complete.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge