# CVE-2026-13762: AWS CloudFront WAF bypass via HTTP/2 request body fragmentation

Source: https://junglewise.ai/threats/cve-2026-13762-aws-cloudfront-waf-bypass-via-http-2-request-body-fragmentation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-29. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-13762 · Severity: critical · CVSS 9.8 · Published 2026-06-29

AWS WAF is a web application firewall that protects customer applications from common web attacks. A flaw in how AWS WAF processes HTTP/2 multi-frame requests allows attackers to bypass request body inspection, potentially enabling malicious payloads to reach the protected application undetected.

Technologies: [Amazon AWS](https://junglewise.ai/threats/technologies/aws). Vendors: [Amazon](https://junglewise.ai/threats/vendors/amazon), [Amazon Web Services](https://junglewise.ai/threats/vendors/amazon-web-services).

## Quick answers

**Is CVE-2026-13762 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-13762 being exploited in the wild.

**How severe is CVE-2026-13762?** Critical severity, with a CVSS score of 9.8, published 29 June 2026.

**Which products and versions are affected?** Amazon Web Services CloudFront All versions prior to 2026-06-29 remediation.

**Is there a fix for CVE-2026-13762?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-13762 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-13762?** Check whether you run Amazon AWS or Amazon Web Services CloudFront at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

This vulnerability affects AWS WAF's ability to properly inspect request bodies in HTTP/2 multi-frame requests. The issue stems from improper handling of fragmented HTTP/2 frames when reconstructing the full request body for security inspection. An attacker can craft a specially-structured multi-frame HTTP/2 request that causes AWS WAF to fail to properly reassemble or inspect the request body, allowing bypass of WAF rules that would normally block malicious payloads. This requires network access to an application protected by AWS WAF and the ability to send crafted HTTP/2 requests. The impact is that web-based attacks (SQL injection, XSS, etc.) embedded in request bodies could bypass WAF protection. Patches are expected from AWS.

## Affected products

- Amazon Web Services AWS WAF

## Timeline

- 2026-09-22: disclosed

## References

- [https://aws.amazon.com/security/security-bulletins/rss/2026-048-aws/](https://aws.amazon.com/security/security-bulletins/rss/2026-048-aws/)

## Related threats

- [An untrusted search path issue in Aurora PostgreSQL dialect detection in the AWS Advanced Go Wrapper from release 2026-04-06 (awssql/v2.0.0)](https://junglewise.ai/threats/cve-2026-126793-privilege-escalation-in-aurora-postgresql-dialect-detection-in)
- [AWS SDK for pandas EMR unverified bucket ownership](https://junglewise.ai/threats/cve-2026-127119-unverified-ownership-of-the-default-emr-cluster-log-location-in)
- [Amazon mcp-gateway-registry server-side request forgery in registration API](https://junglewise.ai/threats/cve-2026-125926-server-side-request-forgery-in-the-server-registration-and)
- [Amazon mcp-gateway-registry authorization bypass in management API](https://junglewise.ai/threats/cve-2026-100307-missing-authorization-on-the-external-management-api-in-mcp)
- [AWS Kiro CLI incorrect default permissions on session files](https://junglewise.ai/threats/cve-2026-124848-incorrect-default-permissions-on-session-transcripts-and-prompt)