Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.9

AWS Load Balancer: HTTP/2 Bypass of WAF Inspection

CVE-2026-13763 · published 4 months ago
Summary

Some AWS load balancers might not properly check requests if they use a new internet protocol. This can let hackers get past security rules. To fix this, make sure your load balancer is set to inspect requests fully, as described in the AWS documentation.

Original advisory text
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 requ...
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 )
References
Fix within
Internet-facing 3 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically
  • Gives an attacker full control
Severity
7.9 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-444Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Timeline
Published29 Jun 2026
Updated4 Nov 2026
First seen29 Jun 2026
Sources
CVE-2026-13763 · NVD
Track software like this
Free during beta