CVE-2026-49753: Elixir Integer Parse Http Smuggling
Using `Integer.parse/1` or `Integer.parse/2` to parse `Content-Length` or other HTTP length headers can leave the application vulnerable to HTTP Request/Response Smuggling. Elixir's `Integer.parse` accepts an optional `+` or `-` prefix, which violates RFC 7230's strict digital-only format for lengths. A proxy may parse this strictly while this application pa
Elixirgreprules fetch cve-2026-49753-elixir-integer-parse-http-smuggling --engine opengrepDescription
Using `Integer.parse/1` or `Integer.parse/2` to parse `Content-Length` or other HTTP length headers can leave the application vulnerable to HTTP Request/Response Smuggling. Elixir's `Integer.parse` accepts an optional `+` or `-` prefix, which violates RFC 7230's strict digital-only format for lengths. A proxy may parse this strictly while this application pa
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.