CVE-2026-22779Medium▾ SunlitBlackSheep's ClientSession is vulnerable to CRLF injection
▾ Sunlit zone — Low / medium · no exploitation signal
impact 27.5 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.3%
0.3% → 0.4%
The HTTP Client implementation in BlackSheep is vulnerable to CRLF injection. Missing headers validation makes it possible for an attacker to modify the HTTP requests (e.g. insert a new header) or even create a new HTTP request. Exploitation requires developers to pass unsanitized user input directly into headers. The server part is not affected because BlackSheep delegates to an underlying ASGI server handling of response headers.
Attack vector: Applications using user input in HTTP client requests (method, URL, headers).
Users who use the HTTP Client in BlackSheep should upgrade to 2.4.6.
If users handle headers from untrusted parties, they might reject values for header names and values that contain carriage returns.
https://owasp.org/www-community/vulnerabilities/CRLF_Injection
blacksheep < 2.4.6Upgrade to a patched release:
blacksheep 2.4.6