{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-13763 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13763 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-13763 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-13763 in the wild and no public exploit code.\n\nAffected product: AWS Application Load Balancer. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-13763/ (Markdown: https://insights.sbomify.com/CVE-2026-13763/index.md)","id":"CVE-2026-13763","markdown":"https://insights.sbomify.com/CVE-2026-13763/index.md","name":"CVE-2026-13763","record":{"aliases":["GHSA-9m3p-hghr-5v6c"],"analysis":{"component_type":"cloud_service","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"AWS Application Load Balancer","requires_auth":"none","summary":"Remote attackers can bypass AWS WAF body inspection on HTTP/2 ALB target groups by fragmenting request bodies, requiring configuration changes to mitigate.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[{"product":"application_load_balancer","vendor":"amazon"}],"cvss":{"score":7.9,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"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.\n\nTo 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 )","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"HTTP/2 Stream Parser Confusion Body-Inspection Bypass in AWS Application Load Balancer with AWS WAF","id":"CVE-2026-13763","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in LearnPress – WordPress LMS Plugin for Create and Sell Online Courses","id":"CVE-2026-13765"},"packages":[],"prev":{"headline":"HTTP/2 Stream Parser Confusion Body-Inspection Bypass in Amazon CloudFront with AWS WAF","id":"CVE-2026-13762"},"products":["AWS Application Load Balancer"],"published":"2026-06-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-29","vendors":["AWS"]},"summary":"Remote attackers can bypass AWS WAF body inspection on HTTP/2 ALB target groups by fragmenting request bodies, requiring configuration changes to mitigate.","url":"https://insights.sbomify.com/CVE-2026-13763/"}