CVEs.
Vulnerabilities published in the last two years in software made by the companies on the wall: clients, SDKs, agents and self-hosted editions. A CVE here does not mean the hosted service was affected or breached.
NVD data refreshed 2 h ago
Severity of matching CVEs
CVSS base severity, as scored in NVD
- Critical
- 00%
- High
- 8100%
- Medium
- 00%
- Low or not scored
- 00%
- Matching CVEs
- 8
- Last two years
- Critical
- 0
- CVSS 9.0 and above
- High
- 8
- CVSS 7.0 to 8.9
- Known exploited
- 0
- On CISA's KEV list
Matching CVEs published
By month, last two years
Peak 4 · July 2026
- Total: 8
- December 2024: 0
- January 2025: 0
- February 2025: 0
- March 2025: 0
- April 2025: 0
- May 2025: 1
- June 2025: 0
- July 2025: 0
- August 2025: 0
- September 2025: 0
- October 2025: 0
- November 2025: 0
- December 2025: 1
- January 2026: 0
- February 2026: 0
- March 2026: 1
- April 2026: 0
- May 2026: 0
- June 2026: 1
- July 2026: 4
- August 2026: 0
- September 2026: 0
- October 2026: 0
- November 2026: 0
Most CVEs
In each company's software, last two years
Matching CVEs
- 8.0High
CVE-2026-14541 (opens in a new tab)
An authentication bypass and audience confusion vulnerability exists in the Google OAuth provider component of Google mcp-toolbox version 1.4.0. When a Google authService is initialized with mcpEnabled: true but lacks an explicitly defined audience or clientId, the ValidateMCPAuth pipeline for opaque tokens skips audience validation entirely. As a result, the toolbox will accept any valid Google OAuth access token—even those minted for unrelated ecosystem applications—granting unauthorized clients access to protected tools and data backends.
Google Cloud· Jul 31, 2026
- 8.0High
CVE-2026-14540 (opens in a new tab)
A Server-Side Request Forgery (SSRF) vulnerability exists in the generic HTTP source and tool components of Google mcp-toolbox versions 0.3.0 through 1.4.0. While the toolbox implements baseline input sanitization for user-controlled parameters, the underlying HTTP client (internal/sources/http/http.go) fails to safely regulate request redirection boundaries. Specifically, the client is initialized without a restrictive CheckRedirect policy hook and lacks target IP validation. An attacker or a malicious data-driven prompt can supply a crafted path parameter that triggers an open redirect or a
Google Cloud· Jul 31, 2026
- 8.1High
CVE-2026-14537 (opens in a new tab)
Incorrect Authorization in the direct HTTP API tool invocation endpoint in Google mcp-toolbox versions v1.3.0 and v1.4.0 allows an unauthenticated attacker to invoke tools protected by the scopeRequired feature via sending tool invocation requests through legacy HTTP endpoints when the --enable-api flag is active.
Google Cloud· Jul 31, 2026
- 8.6High
CVE-2026-15829 (opens in a new tab)
A SQL injection (CWE-89) and security boundary bypass (CWE-863) vulnerability exists in the prebuilt BigQuery forecasting tool (bigquery-forecast) of googleapis/mcp-toolbox. The tool accepts client-controlled parameters (data_col, timestamp_col, and id_cols) as plain strings and interpolates them unescaped via fmt.Sprintf directly into a generated AI.FORECAST table-valued SELECT statement. While MCP Toolbox utilizes an allowedDatasets mechanism to restrict queries, this defense only validates the history_data parameter; the final assembled query is executed without re-validation. An attacker c
Google Cloud· Jul 21, 2026
- 8.6High
CVE-2026-11719 (opens in a new tab)
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 head
Google Cloud· Jun 18, 2026
- 8.6High
CVE-2026-3136 (opens in a new tab)
An improper authorization vulnerability in GitHub Trigger Comment Control in Google Cloud Build prior to 2026-1-26 allows a remote attacker to execute arbitrary code in the build environment. This vulnerability was patched on 26 January 2026, and no customer action is needed.
Google Cloud· Mar 3, 2026
- 8.6High
CVE-2025-13428 (opens in a new tab)
A vulnerability exists in the SecOps SOAR server. The custom integrations feature allowed an authenticated user with an "IDE role" to achieve Remote Code Execution (RCE) in the server. The flaw stemmed from weak validation of uploaded Python package code. An attacker could upload a package containing a malicious setup.py file, which would execute on the server during the installation process, leading to potential server compromise. No customer action is required. All customers have been automatically upgraded to the fixed version: 6.3.64 or higher.
Google Cloud· Dec 9, 2025
- 8.7High
CVE-2025-4600 (opens in a new tab)
A request smuggling vulnerability existed in the Google Cloud Classic Application Load Balancer due to improper handling of chunked-encoded HTTP requests. This allowed attackers to craft requests that could be misinterpreted by backend servers. The issue was fixed by disallowing stray data after a chunk, and is no longer exploitable. No action is required as Classic Application Load Balancer service after 2025-04-26 is not vulnerable.
Google Cloud· May 16, 2025
Public information only
Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.
Sources
- National Vulnerability Database (opens in a new tab): CVE IDs, descriptions, publication dates and CVSS severity, published by the U.S. government (NIST)
- CISA Known Exploited Vulnerabilities catalog (opens in a new tab): the "Known exploited" flag
How fresh it is
- New and changed CVEs: pulled from NVD every two hours; last run 2 h ago
- Known-exploited flags: updated from CISA in the same run
- Window: the last two years; older entries drop off automatically
Source: the U.S. National Vulnerability Database, refreshed daily, with the known-exploited flag from CISA's KEV catalog. Descriptions are NVD's. A CVE is listed under a company when NVD names that company's product as affected, or when the company's own CVE authority assigned it; companies whose names are common words are matched only by explicit rules, so some CVEs will be missing. This product uses NVD data but is not endorsed or certified by the NVD. CVE is a registered trademark of The MITRE Corporation.
statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.