Skip to main content
cve.nowby Sazabi
Menu
CVEs

CVE

Red Hat Enterprise Linux local privilege escalation in ABRT dump handling

Affects Red Hat Enterprise Linux 6, 7 and 8 systems where ABRT dump directories are processed by privileged handlers. CVSS scores it 7.8 (high). No fixed version or patch is listed.

CVE-2026-110331EUVD-2026-125778

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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

7.8HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Dump directories are handled by privileged ABRT handlers while processing them

Published
Last modified
Reference
Last checked
0.10% · 0th percentile
28/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

The abrt package in Red Hat Enterprise Linux is affected. A local user with a low-privilege account, and no user action needed, can create a "count" element in a dump directory to bypass an incomplete fix for CVE-2026-54228 and CVE-2026-54229, then add or change elements in that directory or take ownership of it while privileged abrt handlers process it.

Original 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.

Who should check

Local users and admins of Red Hat Enterprise Linux systems that keep abrt installed, since ABRT handlers process dump directories.

“Restrict local interactive user access on systems that keep abrt installed.”

access.redhat.com

cve.now Index

28Pcve.now Index 28 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach10/20Shipped in major Linux distributions
  • Severity7.8/10CVSS 7.8
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

  • Check whether your setup matches what the bug needs.

    Dump directories are handled by privileged ABRT handlers while processing them

  • Workaround: Disable or remove ABRT if not required, or restrict local interactive user access on systems that keep abrt installed.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-110331 (Abrt: abrt: incomplete cve-2026-54228/54229 fix — completeness gate bypassed via attacker-supplied count element), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-110331 (entry last updated 2026-11-13):
Affected:
- Red Hat Red Hat Enterprise Linux 6: version range not reported
- Red Hat Red Hat Enterprise Linux 7: version range not reported
- Red Hat Red Hat Enterprise Linux 8: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Dump directories are handled by privileged ABRT handlers while processing them (source: https://access.redhat.com/security/cve/cve-2026-110331)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
Workaround: Disable or remove ABRT if not required, or restrict local interactive user access on systems that keep abrt installed. (source: https://www.cve.org/CVERecord?id=CVE-2026-110331)
CISA KEV: CVE-2026-110331 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110331 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2552067
- https://access.redhat.com/security/cve/CVE-2026-110331
- https://www.cve.org/CVERecord?id=CVE-2026-110331
- https://access.redhat.com/security/cve/cve-2026-110331
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-110331
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110331"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • abrt

    Version range not reported

  • abrt

    Version range not reported

  • abrt

    Version range not reported

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Report

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-110331

Is CVE-2026-110331 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A local attacker can bypass the completeness guard and again poison elements in, or seize ownership of, dump directories while privileged ABRT handlers process them.Source: access.redhat.com, cve.org

Am I affected, and how do I check?

The listed products are Red Hat Enterprise Linux 6, 7 and 8. The exposure depends on ABRT handlers processing dump directories with privileged rights, so check whether the ABRT services (abrtd.service, abrt-journal-core.service, abrt-oops.service, abrt-xorg.service) are installed and enabled, for example with systemctl status abrtd.service.Source: access.redhat.com, cve.org

How do I fix CVE-2026-110331?

The facts list no fixed versions or patch identifiers for this vulnerability. The advisory's only stated mitigation is to disable or remove ABRT if it is not required.Source: access.redhat.com, cve.org

What if there's no patch?

Disable or remove ABRT if it is not required, using systemctl disable --now on abrtd.service, abrt-journal-core.service, abrt-oops.service and abrt-xorg.service. On systems that keep abrt installed, restrict local interactive user access.Source: access.redhat.com, cve.org

Sources

More CVEs

Related