Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network attack vector, low complexity, no privileges required, no user interaction, low integrity impact only.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
1DescriptionCVE.org
tiny-http through 0.12.0 contains an HTTP header injection vulnerability that allows attackers to inject carriage return (0x0D) and line feed (0x0A) bytes into HTTP header values on both request and response sides due to insufficient validation in header parsing and serialization. Attackers can exploit this injection primitive to perform response splitting, cache poisoning, session fixation via Set-Cookie injection, security header override, and request smuggling against line-feed-tolerant backends.
AnalysisAI
Header injection vulnerability in tiny-http through version 0.12.0 allows attackers to inject CRLF bytes into HTTP header values, enabling response splitting, cache poisoning, and session fixation. No active exploitation reported, but proof-of-concept code is publicly available in a GitHub repository. The library's insufficient validation of header values enables this injection primitive against line-feed-tolerant backends.
Technical ContextAI
The vulnerability is a CRLF injection (CWE-113) in the HTTP header parsing and serialization logic of tiny-http, a Rust library for handling HTTP requests and responses. The library fails to strip or reject carriage return (0x0D) and line feed (0x0A) bytes from header values, allowing attackers to inject arbitrary headers and body content. This injection occurs at the protocol level, affecting both request and response headers. The CPE data is not available, but the affected product is the tiny-http crate up to version 0.12.0. The root cause is insufficient input validation, a classic class of injection vulnerabilities in text-based protocols.
RemediationAI
No vendor-released patch identified at time of analysis. As a workaround, implement strict input validation on all header values by stripping or rejecting carriage return (0x0D) and line feed (0x0A) bytes before passing them to tiny-http's header parsing functions. Additionally, ensure that any application-level header generation (e.g., reflecting user input) sanitizes output. Consider replacing tiny-http with an actively maintained HTTP library that enforces proper CRLF handling. These mitigations may require code changes but do not affect basic HTTP functionality; however, removing support for legitimate multi-line headers (though rare) could break some backends. Regularly monitor the tiny-http repository for future security patches.
Same weakness CWE-113 – HTTP Response Splitting
View allSame technique Code Injection
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-49883
GHSA-5wm6-g4fr-88x8