How severe is GHSA-76g7-m3xw-x9gr?

No CVSS score has been assigned to GHSA-76g7-m3xw-x9gr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-76g7-m3xw-x9gr?

GHSA-76g7-m3xw-x9gr affects the following packages: github.com/googleapis/mcp-toolbox (Go). Ecosystems affected: Go.

How do I fix GHSA-76g7-m3xw-x9gr?

Update github.com/googleapis/mcp-toolbox to 0.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-76g7-m3xw-x9gr is resolved across your whole dependency graph.

How do I detect GHSA-76g7-m3xw-x9gr 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-76g7-m3xw-x9gr 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-76g7-m3xw-x9gr actively exploited in the wild?

No public exploit code has been indexed for GHSA-76g7-m3xw-x9gr 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-76g7-m3xw-x9gr?

GHSA-76g7-m3xw-x9gr has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 11th 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-76g7-m3xw-x9gr?

GHSA-76g7-m3xw-x9gr is classified as CWE-346 (CWE-346). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-76g7-m3xw-x9gr published, and has it been updated?

GHSA-76g7-m3xw-x9gr was published on June 13, 2026 and was last updated on September 10, 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

MCP Toolbox for Databases has an Origin Validation ErrorGHSA-76g7-m3xw-x9gr

Fix: googleapis/mcp-toolbox#2254

GHSA-76g7-m3xw-x9gr is a CWE-346 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.

Also known asCVE-2026-11624GO-2026-6288

Published

Jun 13, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 9, 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-76g7-m3xw-x9gr.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs11th percentile — riskier than 11% 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

The Model Context Protocol has a security warning advising servers to validate the "Origin" header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin's host. In v0.25.0, a new "--allowed-hosts" flag was introduced alongside the existing "--allowed-origins" flag, enabling users to specify permitted hosts at server startup. Both flags default to "", allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to "", the server will output a startup warning about potential vulnerabilities. Documentation has also been updated to highlight these security considerations.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/googleapis/mcp-toolbox`	all versions	0.25.0`go get github.com/googleapis/mcp-toolbox@v0.25.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 0.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-76g7-m3xw-x9gr 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

The Model Context Protocol has a security warning advising servers to validate the "Origin" header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin's host. In v0.25.0, a new "--allowed-hosts" flag was introduced alongside the existing "--allowed-origins" flag, enabling users to specify permitted hosts at server startup. Both flags default to "*", allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to "*", the server will output a startup warning ab

O3 Security · Impact-Aware SCA

Is GHSA-76g7-m3xw-x9gr in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works