CVE-2026-38967 Details
Description
CrowCpp Crow through v1.3.1 HTTP is vulnerable to response header injection via unvalidated response header values.
A response header injection vulnerability has been identified in CrowCpp Crow versions through 1.3.1. This issue allows for HTTP response header injection or response splitting, as the application does not validate response header values before including them in the HTTP response. The vulnerability arises because user-supplied header values can be directly added to the response header map without proper sanitization, allowing carriage return and line feed characters to be injected and interpreted as separate header lines.
Users can update to CrowCpp Crow version 1.3.2, which includes a patch for this vulnerability by sanitizing CR/LF characters in response headers.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jun 2, 2026CISA-ADP
Assessed Jun 3, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/CrowCpp/Crow/issues/1165 | [email protected] | ExploitIssue TrackingTechnical DescriptionVendor |
| https://github.com/CrowCpp/Crow/pull/1167 | [email protected] | Source CodeVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-113 | Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| CrowCpp Crow | <= 1.3.1 (semver) |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 22, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 3, 2026 | CVE Modified | CISA-ADP |
| Jun 2, 2026 | New CVE Received | [email protected] |
Volerion