CVE-2026-47069
Received Received - Intake
CRLF Injection in hackney HTTP Library

Publication date: 2026-05-25

Last updated on: 2026-05-25

Assigner: EEF

Description
Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in benoitc hackney allows HTTP Response Splitting. The hackney_cookie:setcookie/3 function in src/hackney_cookie.erl validates the Name and Value arguments against CRLF and control characters, but concatenates the domain and path options verbatim into the output iolist with no equivalent check. An attacker who controls either option β€” for example by supplying a Host header value forwarded as the cookie domain, or a request path forwarded as the cookie path β€” can inject a literal CRLF sequence and arbitrary additional Set-Cookie headers into the HTTP response. This issue affects hackney: from 0.9.0 before 4.0.1.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-25
Last Modified
2026-05-25
Generated
2026-05-26
AI Q&A
2026-05-26
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
benoitc hackney From 0.9.0 (inc) to 4.0.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-93 The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is an Improper Neutralization of CRLF Sequences, also known as CRLF Injection, found in the benoitc hackney library. Specifically, the hackney_cookie:setcookie/3 function validates the Name and Value arguments to prevent CRLF and control characters, but it does not validate the domain and path options before concatenating them into the HTTP response. An attacker who can control either the domain or pathβ€”such as by manipulating the Host header or request pathβ€”can inject CRLF sequences and additional Set-Cookie headers into the HTTP response, leading to HTTP Response Splitting.


How can this vulnerability impact me? :

This vulnerability can allow an attacker to perform HTTP Response Splitting by injecting CRLF sequences into HTTP responses. This can lead to security issues such as web cache poisoning, cross-site scripting (XSS), session fixation, or other attacks that rely on manipulating HTTP headers or responses.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart