CVE-2026-110331

Abrt: abrt: incomplete cve-2026-54228/54229 fix — completeness gate bypassed via attacker-supplied count element

  • High 7.8

Description

A flaw was found in abrt. The completeness check introduced to mitigate CVE-2026-54228 and CVE-2026-54229 only verifies that a dump directory contains a "count" element, which an unprivileged user can create. This allows a local attacker to bypass the guard and again poison elements in, or seize ownership of, dump directories while privileged ABRT handlers are processing them. Related Problems2 mutating methods remain ungated by the same check.

Key facts

Published
13 Nov 2026
Last changed
13 Nov 2026
Assigned by
redhat
EPSS
0.101% likely to be exploited in the next 30 days, higher than 0.922% of CVEs (scores for 15 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.8CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What to do

  • Disable or remove ABRT if not required: systemctl disable --now abrtd.service abrt-journal-core.service abrt-oops.service abrt-xorg.service. Restrict local interactive user access on systems that keep abrt installed. Note that abrt-dbus is D-Bus activatable even when abrtd is stopped.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 6
  • Default status: unknown
Red HatRed Hat Enterprise Linux 7
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected

Timeline

  1. 26 Jul 2026 Reported to Red Hat.
  2. 13 Nov 2026 Made public.
  3. 13 Nov 2026 Published

Weakness

References