How many CVEs have patched InitializeConfigs?

1 published CVEs changed InitializeConfigs in googleapis/mcp-toolbox, in 1 distinct patches totalling 9 changed lines, between 2026 and 2026.

What is the latest CVE that changed InitializeConfigs?

CVE-2026-14537 (Authorization Bypass in MCP Toolbox Legacy HTTP Endpoints), published 2026-07-31, changed lines 77 to 150 of internal/server/server.go.

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

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

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

Function

InitializeConfigs

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

internal/server/server.go

Last patched July 31, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

9

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

InitializeConfigs in googleapis/mcp-toolbox was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 9 lines in total.

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

CVEs that patched it

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

Authorization Bypass in MCP Toolbox Legacy HTTP Endpoints
CVE-2026-14537 · lines 77–150 · +9 −0 in 2 hunks
High · CVSS 8.1
EPSS 0.3%2026-07-31

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 file 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 InitializeConfigs.

How many CVEs have patched InitializeConfigs?: 1 published CVEs changed InitializeConfigs in googleapis/mcp-toolbox, in 1 distinct patches totalling 9 changed lines, between 2026 and 2026.
What is the latest CVE that changed InitializeConfigs?: CVE-2026-14537 (Authorization Bypass in MCP Toolbox Legacy HTTP Endpoints), published 2026-07-31, changed lines 77 to 150 of internal/server/server.go.
How does InitializeConfigs compare to the rest of googleapis/mcp-toolbox?: googleapis/mcp-toolbox has 14 CVEs with a located fix in total; 1 of them changed InitializeConfigs.
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