# CVE-2026-128987: Dbus: infinite cpu-spin loop in libdbus socket transport when epipe is received during write operations


- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-128987, ECHO-eb0e-7c69-1b80, GHSA-4734-9v83-3gjc, UBUNTU-CVE-2026-128987

## What is CVE-2026-128987?

CVE-2026-128987 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 13 Nov 2026. 

### Official description

A flaw was found in dbus. A local attacker can exploit this vulnerability by connecting to an affected service, requesting a response, and stopping socket reads while keeping the connection open. Because the socket transport handles broken pipe write errors as retryable, the application enters a continuous retry loop. This can lead to excessive CPU consumption, resulting in a denial of service (DoS) for the target process.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2026-128987?


## How do I fix CVE-2026-128987?

Upgrade to a fixed version.

## Is CVE-2026-128987 being exploited?

There is no known exploitation of CVE-2026-128987 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128987 and fix it if it is affected.

What it is: CVE-2026-128987 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128987 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128987/ (Markdown: https://insights.sbomify.com/CVE-2026-128987/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128987
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128987
- OSV: https://osv.dev/vulnerability/CVE-2026-128987

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128987/
Summaries are generated and may contain mistakes; the official description above is the record.
