Quick answers
- Is CVE-2026-14537 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14537 being exploited in the wild.
- How severe is CVE-2026-14537?
- Informational severity, with a CVSS score of 8.1, published 31 July 2026.
- Which products and versions are affected?
- Google MCP Toolbox v1.3.0, v1.4.0.
- Is there a fix for CVE-2026-14537?
- A patch was published on 2026-06-18: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-14537 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-14537?
- Check whether you run Google MCP Toolbox 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.
Technical details
An incorrect authorization vulnerability (CWE-863) exists in Google mcp-toolbox v1.3.0 and v1.4.0 within the direct HTTP API tool invocation endpoint. When the '--enable-api' flag is active, the application fails to properly enforce 'scopeRequired' authorization policies on legacy HTTP endpoints. An unauthenticated remote attacker can exploit this by sending tool invocation requests through these legacy endpoints, effectively bypassing intended access controls. The issue has been addressed in subsequent updates by introducing a startup validation check that prevents the server from running if both MCP Authorization and the legacy HTTP API are enabled simultaneously.
Affected products
- Google mcp-toolbox v1.3.0, v1.4.0
Timeline
- 2026-06-15: disclosed: Issue reported and PR created
- 2026-06-18: patched: Fix merged into main branch
- 2026-07-31: advisory: CVE published to NVD