VulnerabilityPublished 13 Nov 2026

CVE-2026-128987: Red Hat Enterprise Linux 10 · Loop with Unreachable Exit Condition

Affects Red Hat Enterprise Linux 10Source CVE Database V5

Compare

Not known to be exploited · CVSS 6.2 Medium.

Data as of 13 Nov 2026, 21:20 UTC

CVSS 3.1 base score

6.2Medium

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	6.2

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 13 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10dbus	Affected–	Fixed in–

AI-suggested

Red Hat currently does not provide a mitigation or patch that meets their criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat advisories for future updates. No immediate action is available to fully mitigate this vulnerability.

Description

CVE-2026-128987 is a vulnerability in the dbus component of Red Hat Enterprise Linux 10 where a local attacker can cause a denial of service by triggering a continuous retry loop that leads to excessive CPU consumption. The flaw arises when socket writes encounter broken pipe errors treated as retryable, causing the application to spin indefinitely. This impacts process availability but does not allow privilege escalation or data compromise. No effective mitigation or patch is currently available from Red Hat.

Impact

Exploitation results in a denial of service through CPU resource exhaustion of the affected process. There is no impact on confidentiality or integrity, and no privilege escalation is possible. The attack requires local access to interact with the IPC socket. The denial of service is limited to process availability and does not affect the overall system security beyond that.

Summary

This vulnerability affects the dbus socket transport in Red Hat Enterprise Linux 10. A local attacker can exploit it by connecting to an affected service, requesting a response, and then stopping socket reads while keeping the connection open. Because the socket transport treats broken pipe (EPIPE) write errors as retryable, the application enters an infinite retry loop, causing excessive CPU usage and resulting in a denial of service for the target process. The impact is limited to local denial of service without affecting confidentiality or integrity. Red Hat classifies this as a moderate severity issue with a CVSS v3.1 score of 6.2 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Currently, no mitigation or patch meeting Red Hat's criteria is available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 21:20 UTC

Technical details

References

Community reviews

Related threats