Content injection via unsanitized journal output
Published Jun 13, 2026 · Updated Jun 13, 2026
Content injection in ABRT on Red Hat Enterprise Linux 7 and 8 allows local users to control root-written dump-file content via syslog. The post-create scripts query journalctl with _COMM and _UID filters, then copy entries into dump-directory files without removing embedded newlines or validating the resulting lines. Exploitation requires local access and an installed, running ABRT service; it alters diagnostic-file integrity without reported disclosure or service interruption.
Summary
What happened
Content injection in ABRT on Red Hat Enterprise Linux 7 and 8 allows local users to control root-written dump-file content via syslog. The post-create scripts query journalctl with _COMM and _UID filters, then copy entries into dump-directory files without removing embedded newlines or validating the resulting lines. Exploitation requires local access and an installed, running ABRT service; it alters diagnostic-file integrity without reported disclosure or service interruption.
The record
- CVE
- CVE-2026-54231
- Published
- Jun 13, 2026
- Updated
- Jun 13, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 7
- Classifications
- CWE-74, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2026CVE publishedPublication date reported by the CVE source.
- Jun 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo