Request splitting via unsanitized client request fields
Published Jan 14, 2026 · Updated Jan 14, 2026
CRLF injection in the BlackSheep HTTP client before 2.4.6 allows remote attackers to alter or inject outbound HTTP requests. Client request serialization writes header names, header values, URL paths, and query strings without removing carriage-return or line-feed bytes. Exploitation requires a consuming application to pass unsanitized user input into those fields; the server-side response path is unaffected.
Summary
What happened
CRLF injection in the BlackSheep HTTP client before 2.4.6 allows remote attackers to alter or inject outbound HTTP requests. Client request serialization writes header names, header values, URL paths, and query strings without removing carriage-return or line-feed bytes. Exploitation requires a consuming application to pass unsanitized user input into those fields; the server-side response path is unaffected.
The record
- CVE
- CVE-2026-22779
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- Neoteroi
- Product
- BlackSheep
- Classifications
- CWE-113
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 2026Record 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=< 2.4.6
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
No public exploit references are available in this record.
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