CVE-2026-40073: Unvalidated Content Length Limit Bypass
When an HTTP stream handler accumulates payload size and checks it against a `content-length` limit parsed with `Number()`, `parseInt()`, or `parseFloat()`, it can fail open. For chunked requests, missing headers cause these parsers to return `NaN`. Because numeric inequalities evaluate to false against `NaN` (e.g., `size > NaN`), an attacker can circumvent
JSgreprules fetch cve-2026-40073-unvalidated-content-length-limit-bypass --engine opengrepDescription
When an HTTP stream handler accumulates payload size and checks it against a `content-length` limit parsed with `Number()`, `parseInt()`, or `parseFloat()`, it can fail open. For chunked requests, missing headers cause these parsers to return `NaN`. Because numeric inequalities evaluate to false against `NaN` (e.g., `size > NaN`), an attacker can circumvent
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.