CVE-2025-4600

HTTP Request Smuggling in Google Cloud Classic Application Load Balancer due to Improper Chunked Encoding Validation

Description

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.

Category

8.7
CVSS
Severity: High
CVSS 4.0 •
EPSS 0.10%
Affected: Google Cloud Classic Application Load Balancer
Published at:
Updated at:

References

Link Tags
https://cloud.google.com/support/bulletins#gcp-2025-027

Frequently Asked Questions

What is the severity of CVE-2025-4600?
CVE-2025-4600 has been scored as a high severity vulnerability.
How to fix CVE-2025-4600?
To fix CVE-2025-4600, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-4600 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-4600 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-4600?
CVE-2025-4600 affects Google Cloud Classic Application Load Balancer.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.