Research / Finding
bare LF accepted in chunked transfer encoding
F-NGINX-HTTP-REQ-002
Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.
Read the evidence · View in research browse
Recorded evidence
—score not recorded
bare LF accepted in chunked transfer encoding
fixed publicly
details
- Finding IDs
- F-NGINX-HTTP-REQ-002
- Status
- fixed publicly
- Reported via
- private security contact
- Note
- public fix commit f405ef11fde6 on 2025-12-06, first released in nginx 1.29.4 on 2025-12-09. stable 1.28.x appears unpatched as of 1.28.3 (2026-03-24).
F-NGINX-HTTP-REQ-002: Input / state handling. Bare line feeds lead to inconsistent HTTP request framing. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-NGINX-HTTP-REQ-002
Security area (1seal assessment): Semantics. Rejecting bare LF in chunked encoding tightens HTTP message framing and avoids divergent interpretations of request boundaries. Reviewed 21 Sep 2026.
Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.
How this page groups evidence
This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.