VulnerabilityPublished 13 Feb 2026Updated 23 Mar 2026

CVE-2026-2443: Red Hat Enterprise Linux 10 · Out-of-bounds Read

Affects Red Hat Enterprise Linux 10Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% 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:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within 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 13 Feb 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 26 Oct 2026.

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 or the CVSS exploit maturity 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.

microsoft-security-response-ce

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10libsoup3	Affected–	Fixed in–
Red Hat Enterprise Linux 6libsoup	Affected–	Fixed in–
Red Hat Enterprise Linux 7libsoup	Affected–	Fixed in–
Red Hat Enterprise Linux 8libsoup	Affected–	Fixed in–
Red Hat Enterprise Linux 9libsoup	Affected–	Fixed in–

AI-suggested

To mitigate CVE-2026-2443, organizations should first identify all systems running Red Hat Enterprise Linux 10 with libsoup and determine if the embedded SoupServer component is enabled and exposed to network access. Applying vendor-supplied patches or updates for libsoup as soon as they become available is critical. In the absence of patches, disabling or restricting access to services using SoupServer can reduce exposure. Network-level controls such as firewall rules should limit inbound HTTP traffic to trusted sources. Additionally, monitoring HTTP request headers for anomalous or suspicious Range header values can help detect exploitation attempts. Developers and system administrators should review build configurations to avoid enabling vulnerable SoupServer features unnecessarily. Employing memory protection mechanisms and runtime application self-protection (RASP) can provide additional defense layers. Regular security assessments and penetration testing focusing on HTTP header parsing can identify residual risks. Finally, maintaining an inventory of applications using libsoup and ensuring they are updated or replaced if unmaintained will reduce long-term exposure.

Description

A flaw was identified in libsoup, a widely used HTTP library in GNOME-based systems. When processing specially crafted HTTP Range headers, the library may improperly validate requested byte ranges. In certain build configurations, this could allow a remote attacker to access portions of server memory beyond the intended response. Exploitation requires a vulnerable configuration and access to a server using the embedded SoupServer component.

Impact

The primary impact of CVE-2026-2443 is the potential unauthorized disclosure of sensitive information from server memory due to out-of-bounds reads. Organizations running vulnerable versions of Red Hat Enterprise Linux 10 with libsoup's SoupServer enabled may risk leakage of confidential data, which could include sensitive application data, credentials, or cryptographic material residing in memory buffers. While the vulnerability does not enable remote code execution or denial of service, the confidentiality breach can facilitate further attacks such as privilege escalation or lateral movement if attackers obtain critical information. The ease of exploitation (no authentication or user interaction required) combined with network accessibility increases the threat level, especially for internet-facing services. However, the requirement for specific build configurations and the embedded SoupServer component limits the scope to certain deployments. Enterprises relying on GNOME-based applications or custom services using libsoup as an HTTP server are particularly at risk. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the need for proactive mitigation. Failure to address this vulnerability could lead to data breaches, regulatory non-compliance, and reputational damage.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 00:20 UTC

Technical details

References

Community reviews

Related threats