Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-21428: CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection') in yhirose cpp-httplib

0
High
VulnerabilityCVE-2026-21428cvecve-2026-21428cwe-93
Published: Thu Jan 01 2026 (01/01/2026, 17:54:43 UTC)
Source: CVE Database V5
Vendor/Project: yhirose
Product: cpp-httplib

Description

cpp-httplib is a C++11 single-file header-only cross platform HTTP/HTTPS library. Prior to version 0.30.0, the ``write_headers`` function does not check for CR & LF characters in user supplied headers, allowing untrusted header value to escape header lines. This vulnerability allows attackers to add extra headers, modify request body unexpectedly & trigger an SSRF attack. When combined with a server that supports http1.1 pipelining (springboot, python twisted etc), this can be used for server side request forgery (SSRF). Version 0.30.0 fixes this issue.

AI-Powered Analysis

AILast updated: 01/08/2026, 19:10:12 UTC

Technical Analysis

CVE-2026-21428 is a vulnerability classified under CWE-93 (Improper Neutralization of CRLF Sequences) affecting the cpp-httplib library, a widely used C++11 single-header HTTP/HTTPS client and server library. The vulnerability exists in the write_headers function prior to version 0.30.0, where it fails to sanitize CR (carriage return) and LF (line feed) characters in user-supplied HTTP header values. This flaw allows an attacker to inject CRLF sequences into headers, effectively breaking out of the intended header line and injecting additional headers or manipulating the HTTP request body. Such injection can be leveraged to perform SSRF attacks, particularly when the cpp-httplib client communicates with servers supporting HTTP/1.1 pipelining, such as Spring Boot or Python Twisted frameworks. SSRF enables attackers to make arbitrary requests from the vulnerable server to internal or external systems, potentially bypassing firewall restrictions and accessing sensitive internal resources. The vulnerability is remotely exploitable without authentication or user interaction, increasing its risk profile. Although no known exploits are reported in the wild yet, the CVSS 4.0 base score of 7.7 (high severity) reflects the significant impact and ease of exploitation. The issue is resolved in cpp-httplib version 0.30.0 by properly sanitizing header inputs to prevent CRLF injection.

Potential Impact

For European organizations, this vulnerability poses a substantial risk, especially those developing or deploying applications using cpp-httplib versions prior to 0.30.0. Exploitation can lead to SSRF attacks, which may allow attackers to pivot into internal networks, access sensitive data, or interact with internal services not exposed externally. This is particularly critical for sectors such as finance, healthcare, and government, where internal network confidentiality and integrity are paramount. Additionally, organizations using HTTP/1.1 pipelining servers like Spring Boot or Python Twisted in their infrastructure are at increased risk due to the amplification of the SSRF attack vector. The vulnerability could be exploited to bypass perimeter defenses, leading to data breaches, service disruptions, or further exploitation chains. Given the remote and unauthenticated nature of the exploit, the threat surface is broad, affecting any exposed services or applications using the vulnerable library. The absence of known exploits in the wild currently provides a window for proactive mitigation.

Mitigation Recommendations

1. Immediate upgrade of cpp-httplib to version 0.30.0 or later to ensure proper sanitization of HTTP headers. 2. Implement strict input validation and sanitization on all HTTP headers at the application level to prevent CRLF injection, even if the underlying library is patched. 3. Restrict and monitor outbound HTTP requests from internal servers to limit SSRF impact, using network segmentation and egress filtering. 4. Employ Web Application Firewalls (WAFs) or Intrusion Detection Systems (IDS) configured to detect anomalous HTTP header injection patterns and SSRF attempts. 5. Review and harden server configurations, especially for HTTP/1.1 pipelining support, to minimize SSRF exploitation vectors. 6. Conduct security audits and code reviews focusing on HTTP header handling in custom code interfacing with cpp-httplib. 7. Maintain up-to-date threat intelligence and monitor for emerging exploit attempts targeting this vulnerability. 8. Educate development teams about secure HTTP header handling and the risks of CRLF injection.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-29T03:00:29.274Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6956b5dbdb813ff03e73e079

Added to database: 1/1/2026, 5:58:51 PM

Last enriched: 1/8/2026, 7:10:12 PM

Last updated: 2/6/2026, 9:46:08 AM

Views: 48

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats