Response splitting via unchecked CRLF in headers
Published Oct 10, 2025 · Updated Oct 10, 2025
HTTP response splitting in JuliaWeb HTTP.jl before 1.10.19 allows remote attackers to inject headers through crafted CRLF characters. Header construction accepts names and values containing carriage-return and line-feed characters and serializes them into HTTP messages without rejection. Exploitation requires an application to place attacker-controlled data in a request or response header; successful injection enables cache poisoning, XSS, or session fixation.
Summary
What happened
HTTP response splitting in JuliaWeb HTTP.jl before 1.10.19 allows remote attackers to inject headers through crafted CRLF characters. Header construction accepts names and values containing carriage-return and line-feed characters and serializes them into HTTP messages without rejection. Exploitation requires an application to place attacker-controlled data in a request or response header; successful injection enables cache poisoning, XSS, or session fixation.
The record
- CVE
- CVE-2025-61689
- Published
- Oct 10, 2025
- Updated
- Oct 10, 2025
- Vendor
- JuliaWeb
- Product
- HTTP.jl
- Classifications
- CWE-113, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 2025CVE publishedPublication date reported by the CVE source.
- Oct 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.10.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- HTTP.jl header injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo