How severe is GHSA-5gf6-gc35-xjpc?

No CVSS score has been assigned to GHSA-5gf6-gc35-xjpc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5gf6-gc35-xjpc?

GHSA-5gf6-gc35-xjpc affects the following packages: github.com/googleapis/mcp-toolbox (Go). Ecosystems affected: Go.

How do I fix GHSA-5gf6-gc35-xjpc?

Update github.com/googleapis/mcp-toolbox to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5gf6-gc35-xjpc is resolved across your whole dependency graph.

How do I detect GHSA-5gf6-gc35-xjpc in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/googleapis/mcp-toolbox, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5gf6-gc35-xjpc if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-5gf6-gc35-xjpc actively exploited in the wild?

No public exploit code has been indexed for GHSA-5gf6-gc35-xjpc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5gf6-gc35-xjpc?

GHSA-5gf6-gc35-xjpc has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 3th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5gf6-gc35-xjpc?

GHSA-5gf6-gc35-xjpc is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5gf6-gc35-xjpc published, and has it been updated?

GHSA-5gf6-gc35-xjpc was published on June 18, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-5gf6-gc35-xjpc — mcp-toolbox

Fix: googleapis/mcp-toolbox#3049

GHSA-5gf6-gc35-xjpc is a CWE-862 vulnerability in github.com/googleapis/mcp-toolbox. A fix is available for github.com/googleapis/mcp-toolbox — see the affected versions and patch details below.

MCP Toolbox for Databases: authenticated authorization bypass

Also known asCVE-2026-11719GO-2026-5144

Published

Jun 18, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5gf6-gc35-xjpc.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/googleapis/mcp-toolbox

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

An authenticated authorization bypass vulnerability exists in MCP Toolbox for Databases due to missing scope enforcement across older protocol handlers.

While the 2025-11-25 protocol version handler correctly enforces per-tool restrictions defined by scopesRequired, older supported protocol versions (2025-06-18, 2025-03-26, and 2024-11-05) omit this check. An authenticated client with low-privilege tokens (e.g., read) can bypass the intended per-tool scope restrictions and execute high-privilege tools (e.g., admin) simply by specifying an older protocol version in the MCP-Protocol-Version header, or by omitting the header entirely (which causes the server to default to the vulnerable 2024-11-05 handler).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/googleapis/mcp-toolbox`	all versions	1.4.0`go get github.com/googleapis/mcp-toolbox@v1.4.0`

Affected Products

1 product · 1 configurations

Application

mcp toolbox for databasesgoogle

1 version

1.3.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/googleapis/mcp-toolbox, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/googleapis/mcp-toolbox to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5gf6-gc35-xjpc is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

An authenticated authorization bypass vulnerability exists in MCP Toolbox for Databases due to missing scope enforcement across older protocol handlers. While the 2025-11-25 protocol version handler correctly enforces per-tool restrictions defined by scopesRequired, older supported protocol versions (2025-06-18, 2025-03-26, and 2024-11-05) omit this check. An authenticated client with low-privilege tokens (e.g., read) can bypass the intended per-tool scope restrictions and execute high-privilege tools (e.g., admin) simply by specifying an older protocol version in the MCP-Protocol-Version hea

O3 Security · Impact-Aware SCA

Is GHSA-5gf6-gc35-xjpc in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works