CVE-2026-1536: Red Hat Enterprise Linux 10 · CRLF Injection
Affects Red Hat Enterprise Linux 10Source CVE Database V5
Not known to be exploited · CVSS 5.8 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat Enterprise Linux 10 | Affected– | Fixed in– |
| Red HatRed Hat Enterprise Linux 6 | Affected– | Fixed in– |
| Red HatRed Hat Enterprise Linux 7 | Affected– | Fixed in– |
| Red HatRed Hat Enterprise Linux 8 | Affected– | Fixed in– |
| Red HatRed Hat Enterprise Linux 9 | Affected– | Fixed in– |
AI-suggested
To mitigate CVE-2026-1536, organizations should monitor Red Hat advisories and apply patches or updates to libsoup as soon as they become available. In the interim, administrators should audit applications and services that use libsoup for HTTP header construction, specifically those that handle Content-Disposition headers with user-controlled input. Implement strict input validation and sanitization to remove or encode CRLF sequences before including input in HTTP headers. Employ web application firewalls (WAFs) with rules to detect and block HTTP header injection attempts. Review and harden HTTP response handling logic to prevent response splitting. Additionally, consider isolating vulnerable services behind reverse proxies that can sanitize headers or reject malformed requests. Regularly update and patch all components of the web stack to reduce exposure to similar injection vulnerabilities. Finally, conduct security testing and code reviews focused on HTTP header injection vectors to proactively identify and remediate weaknesses.
Description
A flaw was found in libsoup. An attacker who can control the input for the Content-Disposition header can inject CRLF (Carriage Return Line Feed) sequences into the header value. These sequences are then interpreted verbatim when the HTTP request or response is constructed, allowing arbitrary HTTP headers to be injected. This vulnerability can lead to HTTP header injection or HTTP response splitting without requiring authentication or user interaction.