dbcve.org
FedoraOperating system · Fedoraproject

CVE-2026-54230

HIGH · 7.8 CVSS v3.1 Published 2026-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A symlink following vulnerability was found in the ABRT post-create event handler scripts in libreport. Event scripts write output files using shell redirections without the O_NOFOLLOW flag. If the target file is replaced with a symlink, the shell process running as root follows the symlink and writes content to the symlink target, allowing arbitrary file overwrites on the system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A symlink following vulnerability exists in ABRT post-create event handler scripts in libreport. The scripts write output files using shell redirections without the O_NOFOLLOW flag, causing the root-owned shell process to follow any symlink replacing a target file and write content to the symlink target, enabling arbitrary file overwrites.

MitigationReplace shell redirections with open() calls using O_NOFOLLOW flag, or use atomic file operations (e.g., write to temp file then rename) to prevent symlink following. Verify all event handler scripts that perform file writes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 43= 44
Enterprise LinuxOperating system
Affected:= 7.0= 8.0
AbrtApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ABRT or libreport is installed
    Run `rpm -qa | grep -E '(abrt|libreport)'` or check for the presence of /etc/abrt or /usr/libexec/abrt*
    Affected if No ABRT or libreport packages are found, the system is not affected by this specific vulnerability
  2. Identify the installed version of ABRT or libreport
    Run `rpm -q --queryformat '%{VERSION}%{RELEASE}' abrt` or `rpm -q --queryformat '%{VERSION}%{RELEASE}' libreport`
    Affected if The installed version matches Fedora 43, Fedora 44, RHEL 7.0, RHEL 8.0, or is any version of ABRT from the ABRT Project (compare against the affected ranges)
  3. Locate post-create event handler scripts
    Search for event scripts in /etc/abrt/events/ or /usr/libexec/abrt/ and look for files named 'post-create' or similar event handlers that process newly created crash reports
    Affected if No post-create or similar event handler scripts exist, the vulnerability path does not apply
  4. Examine script content for shell redirection without O_NOFOLLOW
    Inspect the contents of post-create event handler scripts for shell redirections (>, >>) used to write output files without symlink protection
    Affected if The scripts contain file write operations using shell redirections that do not use O_NOFOLLOW flag or symlink checks
  5. Determine if ABRT daemon is enabled or running
    Run `systemctl status abrtd` or check if ABRT processes are running (ps aux | grep abrt)
    Affected if ABRT daemon is actively processing events, creating conditions where the symlink following could be exploited during crash report handling

A system is affected if it runs any version of ABRT/libreport from the affected distributions (Fedora 43/44, RHEL 7.0/8.0) or the ABRT Project, has post-create event handler scripts with unprotected file writes, and has ABRT daemon active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace shell redirections with open() calls using O_NOFOLLOW flag, or use atomic file operations (e.g., write to temp file then rename) to prevent symlink following. Verify all event handler scripts that perform file writes.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54230 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data