HTTP.jl vulnerable to CR/LF Injection in URIs
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- —
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
HTTP.jl provides HTTP client and server functionality for Julia, and URIs.jl parses and works with Uniform Resource Identifiers (URIs). URIs.jl prior to version 1.6.0 and HTTP.jl prior to version 1.10.17 allows the construction of URIs containing CR/LF characters. If user input was not otherwise escaped or protected, this can lead to a CRLF injection attack. Users of HTTP.jl should upgrade immediately to HTTP.jl v1.10.17, and users of URIs.jl should upgrade immediately to URIs.jl v1.6.0. The check for valid URIs is now in the URI.jl package, and the latest version of HTTP.jl incorporates that fix. As a workaround, manually validate any URIs before passing them on to functions in this package.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA HTTP.jl (JuliaWeb) Fixed in 1.10.17
Timeline
- 2026-10-02 Threatist record created from CVE-2025-52479
References
More JuliaWeb vulnerabilities
- TI-2025-38120 HTTP.jl vulnerable to Header injection/Response splitting via header construction. CVSS 4.0HIGH 8.7
- TI-2025-32664 GitHub.jl lacks validation for user-provided fields CVSS 4.0MEDIUM 6.6
- TI-2025-32061 GitForge.jl lacks validation for user provided fields CVSS 4.0MEDIUM 6.6
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences