Skip to main content
VulnerabilityPublished Updated

CVE-2026-14537: Google mcp-toolbox · Incorrect Authorization

Affects mcp-toolboxSource GCVE Database

0
Compare
Authoritative record:CVE-2026-14537· High 8.1

Not known to be exploited · CVSS 8.1 High.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubgoogleapis/mcp-toolboxpkg:github/googleapis/mcp-toolboxOther threatsAffected
  • =1.3.0
  • =1.4.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, it is recommended to disable the --enable-api flag or restrict access to the legacy HTTP endpoints to trusted users only to prevent unauthorized tool invocation.

Description

Google mcp-toolbox versions v1.3.0 and v1.4.0 contain an incorrect authorization vulnerability in the direct HTTP API tool invocation endpoint. This flaw allows an unauthenticated attacker to invoke tools that should be protected by the scopeRequired feature by sending requests through legacy HTTP endpoints when the --enable-api flag is enabled. The vulnerability has a high severity with a CVSS score of 9.8, indicating critical impact on confidentiality, integrity, and availability.

References

Community reviews

Loading reviews…