# CVE-2026-13763: HTTP/2 Stream Parser Confusion Body-Inspection Bypass in AWS Application Load Balancer with AWS WAF

> Remote attackers can bypass AWS WAF body inspection on HTTP/2 ALB target groups by fragmenting request bodies, requiring configuration changes to mitigate.

- **Severity:** High 7.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-9m3p-hghr-5v6c

## What is CVE-2026-13763?

CVE-2026-13763 is a high-severity vulnerability in AWS Application Load Balancer, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 )

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2026-13763?

It affects 1 product.


Products: Amazon Application Load Balancer.

## How do I fix CVE-2026-13763?

No fix has been published for CVE-2026-13763 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13763 being exploited?

There is no known exploitation of CVE-2026-13763 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13763 and fix it if it is affected.

What it is: CVE-2026-13763 is a high-severity vulnerability in AWS Application Load Balancer, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13763 in the wild and no public exploit code.

Affected product: AWS Application Load Balancer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13763/ (Markdown: https://insights.sbomify.com/CVE-2026-13763/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13763
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13763
- OSV: https://osv.dev/vulnerability/CVE-2026-13763

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13763/
Summaries are generated and may contain mistakes; the official description above is the record.