Conflicting message framing at the application boundary
Detects Content-Length and Transfer-Encoding still visible together to a wrapped handler. Edge can shadow or deny the request.
WAF · KE-FRAMING-001
Keryn Edge wrapped handler with KERYN_RUNTIME_EDGE=shadow or enforce
Implementation · keryn-runtime/src/edge/waf.ts · a4c9e6563cea6cde3884134a2fc8a7e1a7e36c2f
Source records
- github.com/advisories/GHSA-8h4c-x2wg-6xp8
- github.com/advisories/GHSA-pf96-p4fj-6566
- www.rfc-editor.org/rfc/rfc9112.html
Inspiration stories
- GHSA-8h4c-x2wg-6xp8 / CVE-2026-69204: Http4s Ember accepts Transfer-Encoding combined with Content-Length (CL.TE request smuggling) 2026-09-15 · Headlines archive
- GHSA-pf96-p4fj-6566 / CVE-2026-84380: HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated 2026-09-08 · Headlines archive
Linked Headlines records
2 source records. Each monthly file identifies the relationship and product rule.