WAF bypass via fragmented HTTP/2 request bodies
Published Jun 29, 2026 · Updated Jun 29, 2026
HTTP request parsing inconsistency in Amazon Web Services Application Load Balancer allows remote attackers to bypass AWS WAF body inspection. For WAF-enabled HTTP/2 target groups, ALB submits the available fragment data to AWS WAF before accumulating every DATA frame, so rules inspect only a partial body. Unauthenticated network access to an affected endpoint is sufficient to conceal malicious body content from managed rules, while the backend receives the complete request.
Summary
What happened
HTTP request parsing inconsistency in Amazon Web Services Application Load Balancer allows remote attackers to bypass AWS WAF body inspection. For WAF-enabled HTTP/2 target groups, ALB submits the available fragment data to AWS WAF before accumulating every DATA frame, so rules inspect only a partial body. Unauthenticated network access to an affected endpoint is sufficient to conceal malicious body content from managed rules, while the backend receives the complete request.
The record
- CVE
- CVE-2026-13763
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- Amazon Web Services
- Product
- Application Load Balancer
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 2026Record 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