CVE-2026-54230
Received Received - Intake
Symlink Following in libreport via ABRT Post-Create Scripts

Publication date: 2026-06-13

Last updated on: 2026-06-13

Assigner: Red Hat, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-13
Last Modified
2026-06-13
Generated
2026-06-13
AI Q&A
2026-06-13
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
redhat abrt *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-59 The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-54230 is a symlink following vulnerability in the ABRT (Automatic Bug Reporting Tool) post-create event handler scripts. These scripts write output files using shell redirections without using the O_NOFOLLOW flag, which prevents following symbolic links. Because of this, if an attacker replaces the intended output file with a symbolic link pointing to another file, the root-level shell process will follow the symlink and overwrite the target file. This allows an attacker who controls the dump directory to overwrite arbitrary files on the system.

Impact Analysis

This vulnerability can lead to arbitrary file overwrites on the system by an attacker who has control over the dump directory. For example, an attacker could replace output files with symlinks pointing to sensitive system files such as /var/spool/cron/root. Overwriting such files could allow the attacker to escalate privileges, execute arbitrary code, or disrupt system operations, resulting in a high impact on confidentiality, integrity, and availability.

Detection Guidance

This vulnerability involves symlink following in the ABRT post-create event handler scripts that write output files without the O_NOFOLLOW flag, allowing arbitrary file overwrites if the target files are replaced with symlinks.

To detect this vulnerability on your system, you can check for the presence of symlinks in the dump directory used by ABRT, typically where output files are written (e.g., $DUMP_DIR).

  • Use the command: find /path/to/dump_dir -type l -ls to list symbolic links in the dump directory.
  • Check the ABRT event handler scripts for usage of shell redirections writing to files without O_NOFOLLOW by reviewing /etc/libreport/events.d/abrt_event.conf and related scripts.
  • Verify if any critical system files (e.g., /var/spool/cron/root) have been replaced or linked via symlinks from the dump directory.
Mitigation Strategies

Immediate mitigation steps include preventing attackers from controlling or placing symlinks in the dump directory used by ABRT event scripts.

  • Restrict write permissions on the dump directory to trusted users only.
  • Manually inspect and remove any suspicious symlinks in the dump directory.
  • Apply any available patches or updates from your vendor that fix the symlink following issue by adding the O_NOFOLLOW flag in the event handler scripts.
  • Consider temporarily disabling the ABRT event handler scripts until a patch is applied.
Compliance Impact

The vulnerability allows an attacker with control over the dump directory to overwrite arbitrary files on the system, including sensitive system files. This could lead to unauthorized modification or corruption of critical data.

Such unauthorized file overwrites may compromise the integrity and confidentiality of data, potentially violating compliance requirements under standards like GDPR and HIPAA, which mandate protection of sensitive information and system integrity.

However, the provided information does not explicitly state the direct impact on compliance with these regulations.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54230. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart