# CVE-2026-54228: Abrt: toctou race condition in abrt-dbus setelement allows arbitrary file writes to dump directories

> Local attackers can exploit a race condition in abrt-dbus to write arbitrary files to root-owned directories, potentially leading to privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-6pjg-wmm6-r8rp

## What is CVE-2026-54228?

CVE-2026-54228 is a high-severity vulnerability in Red Hat Enterprise Linux 6, published on 13 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A time-of-check time-of-use (TOCTOU) race condition was found in the abrt-dbus D-Bus service's SetElement method. Between dump directory creation and post-create event execution, any local user can call SetElement to write arbitrary text files into the root-owned dump directory, bypassing package validation and allowing crashes of unpackaged binaries to survive post-create processing.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

Apply the vendor's patch.

## Is CVE-2026-54228 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54228 is a high-severity vulnerability in Red Hat Enterprise Linux 6, published on 13 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54228 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 6. 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-54228/ (Markdown: https://insights.sbomify.com/CVE-2026-54228/index.md)
```

## Sources

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

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