Request smuggling via oversized chunk-body parsing
Published May 16, 2025 · Updated Sep 8, 2025
HTTP request smuggling in Google Cloud Classic Application Load Balancer before April 26, 2025 allows remote attackers to alter backend requests. Its chunked-body parser accepts oversized chunks and ignores trailing bytes that an upstream server can reinterpret as a line terminator. Exploitation requires a crafted chunked request and differing backend message-boundary parsing, allowing hidden bytes to become a separate request.
Summary
What happened
HTTP request smuggling in Google Cloud Classic Application Load Balancer before April 26, 2025 allows remote attackers to alter backend requests. Its chunked-body parser accepts oversized chunks and ignores trailing bytes that an upstream server can reinterpret as a line terminator. Exploitation requires a crafted chunked request and differing backend message-boundary parsing, allowing hidden bytes to become a separate request.
The record
- CVE
- CVE-2025-4600
- Published
- May 16, 2025
- Updated
- Sep 8, 2025
- Vendor
- Google Cloud
- Product
- Classic Application Load Balancer
- Classifications
- CWE-444, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo