CVE-2026-115877: Http Header Value Screen Rejects Nul But Not Cr Lf
This HTTP header-value screen rejects NUL bytes but accepts bare CR or LF bytes in $DATA. A parser that splits header lines only on CRLF keeps a bare CR/LF inside the value, while lenient front-end proxies treat that byte as a line terminator; the framing disagreement lets a hidden header such as Content-Length stay folded into the value and smuggle or re-fr
Pythongreprules fetch cve-2026-115877-http-header-value-screen-rejects-nul-but-not-cr-lf --engine opengrepDescription
This HTTP header-value screen rejects NUL bytes but accepts bare CR or LF bytes in $DATA. A parser that splits header lines only on CRLF keeps a bare CR/LF inside the value, while lenient front-end proxies treat that byte as a line terminator; the framing disagreement lets a hidden header such as Content-Length stay folded into the value and smuggle or re-fr
Community feedback
0 rule-level signals from signed-in users.
- Useful reports
- 0
- Context false positives
- 0
- Metadata suggestions
- 0
Contextual precision
Aggregated from approved scan feedback. False-positive reports describe observed scan contexts, not a global rule verdict.
- Findings observed
- 0
- Projects
- 0
- Reporters
- 0
Precision details are collecting more signed-in reports before verdict counts or ratios are emphasized.
No approved finding verdicts yet.
No scan diagnostics reported yet.