AWS Application Load Balancer
HTTP/2 Stream Parser Confusion Body-Inspection Bypass in AWS Application Load Balancer with AWS WAF
Edge device · Load balancer / ADCproduct or title mentions "load balancer" (medium confidence)
Inconsistent interpretation of HTTP/2 requests in AWS Application Load Balancer with AWS WAF enabled might allow remote actors to bypass AWS WAF managed rule body inspection via crafted HTTP/2 requests that fragment the request body across frames so that only a partial body is inspected. This issue only impacts HTTP/2 ALB target groups. To remediate this issue, customers should enable the "Inspect after sufficient data" target group configuration associated to an ALB load balancer. Refer to: ( https://docs.aws.amazon.com/elasticloadbalancing/latest/application/edit-target-group-attributes.html#waf-http2-inspection )
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- 0
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Mitigation docs.aws.amazon.com/elasticloadbalancing/latest/applica…
- Vendor advisory aws.amazon.com/security/security-bulletins/2026-04…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.