CVE-2026-1467VulnerabilityPublished 27 Jan 2026Updated 25 Mar 2026

CVE-2026-1467: Red Hat Enterprise Linux 10 · CRLF Injection

Affects Red Hat Enterprise Linux 10Source CVE Database V5

Mentioned vulnerabilities

Not known to be exploited · CVSS 5.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% 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:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

usn-8780-1

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-1467, organizations should apply patches or updates from Red Hat as soon as they become available to ensure libsoup properly sanitizes CRLF sequences in URL-decoded input. Until patches are deployed, administrators should review and harden HTTP proxy configurations to restrict or validate incoming URLs and headers, minimizing exposure to untrusted input. Implementing strict input validation and sanitization at the application or proxy level can reduce injection risks. Network-level controls such as Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) should be configured to detect and block suspicious CRLF injection patterns in HTTP traffic. Monitoring proxy logs for anomalous or malformed requests may help identify exploitation attempts. Additionally, segregating proxy services and limiting their exposure to untrusted networks can reduce attack surface. Security teams should educate developers and administrators about secure HTTP header handling and the risks of CRLF injection to prevent similar vulnerabilities in future.

Description

It was discovered that libsoup incorrectly handled certain URLs when using an HTTP proxy. A remote attacker could possibly use this issue to inject arbitrary HTTP headers. (CVE-2026-1467) It was discovered that libsoup did not remove proxy authentication credentials when following HTTP redirects. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-1539) Ahmed Lekssays discovered that libsoup incorrectly parsed certain HTTP requests. A remote attacker could possibly use this issue to obtain sensitive information. (CVE-2026-1801)

Impact

The primary impact of CVE-2026-1467 is on the integrity of HTTP communications passing through proxies using libsoup on Red Hat Enterprise Linux 10. By injecting unauthorized HTTP headers or request bodies, attackers can manipulate how downstream services interpret requests, potentially bypassing security controls such as authentication, caching, or filtering mechanisms. This can lead to unauthorized actions being performed on backend services, session fixation, cache poisoning, or facilitating further attacks such as cross-site scripting or request smuggling. While confidentiality and availability are not directly impacted, the integrity compromise can have cascading effects on application behavior and trustworthiness of HTTP traffic. Organizations relying on HTTP proxies for traffic inspection or routing are particularly vulnerable, especially in environments where untrusted input is proxied. The vulnerability could be exploited in targeted attacks against critical infrastructure, web services, or internal enterprise applications, leading to data manipulation or unauthorized access.

Summary

CVE-2026-1467 identifies a CRLF injection vulnerability in libsoup, an HTTP client library integral to Red Hat Enterprise Linux 10. The vulnerability occurs specifically when an HTTP proxy is configured and libsoup processes URL-decoded input used to construct the Host header without proper sanitization of CRLF sequences. An attacker can craft a malicious URL containing CRLF characters that, when processed, inject additional HTTP headers or even complete HTTP request bodies into the proxied request. This improper neutralization of CRLF sequences enables HTTP header injection, potentially leading to HTTP request smuggling or manipulation of downstream HTTP services. The vulnerability is exploitable remotely without any authentication or user interaction, increasing its risk profile. The CVSS 3.1 base score is 5.8 (medium), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and a scope change with impact on integrity but not confidentiality or availability. No known exploits are reported yet, but the flaw could be leveraged to bypass security controls, poison caches, or manipulate HTTP traffic in complex network environments. The vulnerability highlights the importance of proper input validation and secure handling of HTTP headers in client libraries used in proxy scenarios.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 18:48 UTC

Technical details

References

Community reviews

Related threats