How many CVEs have patched Config?

3 published CVEs changed Config in googleapis/mcp-toolbox, in 3 distinct patches totalling 16 changed lines, between 2026 and 2026.

What is the latest CVE that changed Config?

CVE-2026-14540 (Server-Side Request Forgery via Unrestricted HTTP Redirection in MCP Toolbox), published 2026-07-31, changed lines 64 to 66 of internal/sources/http/http.go.

How does Config compare to the rest of googleapis/mcp-toolbox?

googleapis/mcp-toolbox has 14 CVEs with a located fix in total; 3 of them changed Config.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

googleapis/mcp-toolbox

Type

4 files

Config

Name: Config in googleapis/mcp-toolbox: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Defined in 4 files

Last patched July 31, 2026

3

CVEs

That changed this function

3

Distinct patches

Backports counted once

16

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

Config in googleapis/mcp-toolbox was changed by 3 published CVE fixes in 2026, in 3 distinct patches that added or removed 16 lines in total.

The name occurs in 4 files: internal/tools/serverlessspark/serverlesssparkcreatesparkbatch/serverlesssparkcreatesparkbatch.go, internal/sources/http/http.go, internal/auth/google/google.go, internal/tools/serverlessspark/serverlesssparkcreatepysparkbatch/serverlesssparkcreatepysparkbatch.go.

googleapis/mcp-toolbox has 14 CVEs with a located fix in total, so 21% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed Config, newest first, with the lines each fix touched.

Server-Side Request Forgery via Unrestricted HTTP Redirection in MCP Toolbox
CVE-2026-14540 · internal/sources/http/http.go · lines 64–66 · +3 −0
High · CVSS 8.0
EPSS 0.1%2026-07-31
MCP Toolbox for Databases: authenticated authorization bypass
CVE-2026-11719 · internal/tools/serverlessspark/serverlesssparkcreatepysparkbatch/serverlesssparkcreatepysparkbatch.go · lines 47–48 · +2 −0
High · CVSS 8.6
EPSS 0.1%2026-06-18
MCP Toolbox for Databases: authenticated authorization bypass
CVE-2026-11719 · internal/tools/serverlessspark/serverlesssparkcreatesparkbatch/serverlesssparkcreatesparkbatch.go · lines 47–48 · +2 −0
High · CVSS 8.6
EPSS 0.1%2026-06-18
googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken)
CVE-2026-11717 · internal/auth/google/google.go · lines 38–43 · +6 −3
Critical · CVSS 9.3
EPSS 0.2%2026-06-18

Get an alert when the next CVE fix lands in googleapis/mcp-toolbox, with the patched functions.

Monitor mcp-toolbox CVEs

Other functions in these files

Functions in the same files that CVE fixes also changed.

Other hotspots in the repository

Functions in googleapis/mcp-toolbox changed by the most CVE fixes.

NewServer3 CVEs · internal/server/server.go httpHandler3 CVEs · internal/server/mcp.go validateClaims3 CVEs · internal/auth/generic/generic.go discoverOIDCConfig3 CVEs · internal/auth/generic/generic.go toolsCallHandler2 CVEs · internal/server/mcp/v20251125/method.go Initialize2 CVEs · internal/auth/google/google.go

All patched functions in googleapis/mcp-toolbox

Frequently asked questions

Common questions about CVE fixes to Config.

How many CVEs have patched Config?: 3 published CVEs changed Config in googleapis/mcp-toolbox, in 3 distinct patches totalling 16 changed lines, between 2026 and 2026.
What is the latest CVE that changed Config?: CVE-2026-14540 (Server-Side Request Forgery via Unrestricted HTTP Redirection in MCP Toolbox), published 2026-07-31, changed lines 64 to 66 of internal/sources/http/http.go.
How does Config compare to the rest of googleapis/mcp-toolbox?: googleapis/mcp-toolbox has 14 CVEs with a located fix in total; 3 of them changed Config.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track googleapis/mcp-toolbox CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing