CVE-2026-14539 Google CVE debrief

Who should care

Administrators and users of Google mcp-toolbox versions up to and including 1.4.0 should be aware of this vulnerability and take necessary defensive actions. Affected operators, platforms, vulnerability-management, and security teams should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. This vulnerability may impact managed environments, and owners should be assigned for follow-up. Compensating controls for exposed systems should be reviewed while remediation is scheduled and verified. System memory usage should be monitored, and anomalous processes should be terminated. Regular security audits and vulnerability assessments should be performed to identify potential vulnerabilities. Asset inventory and rollback/change windows should be reviewed to ensure that exposed assets are properly managed. Source tracking should be implemented to monitor for potential attacks. Monitoring, detection, and logs for exposed assets should be reviewed to ensure that they are properly configured. Exceptions should be tracked, and remediated assets should be retested and closed only after evidence is documented. This vulnerability has a medium priority posture, and defensive actions are required to address this vulnerability. The CVE record was published on 2026-07-31T02:16:28.920Z and has not been modified since then. Limited evidence suggests that affected product deployments may exist in managed environments. Confirm whether affected product deployments exist and assign an owner for follow-up. Review compensating controls for exposed systems while remediation is scheduled and verified. Check relevant monitoring, detection, and logs for exposed assets that need extra review. Track exceptions, retest remediated assets, and close the item only after evidence is documented. Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Perform regular security a

Technical summary

The /mcp endpoint handler in Google mcp-toolbox versions up to and including 1.4.0 is vulnerable to a denial of service attack due to an allocation of resources without limits. An unauthenticated attacker can cause a denial of service by submitting a single, massive HTTP request body, leading to an Out-Of-Memory (OOM) error. This vulnerability has a CVSS score of 6.6 and a CVSS severity of MEDIUM. Affected product context includes Google mcp-toolbox versions up to and including 1.4.0.

Defensive priority

Medium-priority defensive actions are required to address this vulnerability.

Recommended defensive actions

• Implement http.MaxBytesReader or pre-read Content-Length enforcement for the /mcp endpoint handler.
• Configure memory limits for the mcp-toolbox service.
• Monitor system memory usage and terminate anomalous processes.
• Restrict access to the /mcp endpoint.
• Perform regular security audits and vulnerability assessments.

Evidence notes

Evidence is limited; verify affected versions and configurations. Defensive verification tasks are recommended. The HTTP handler component of Google mcp-toolbox versions up to and including 1.4.0 is vulnerable to an allocation of resources without limits. An unauthenticated attacker can cause a denial of service by submitting a single, massive HTTP request body, leading to an Out-Of-Memory (OOM) error. Limited evidence suggests that affected product deployments may exist in managed environments. Confirm whether affected product deployments exist and assign an owner for follow-up.

Official resources