CVE-2025-12744: fedora · OS Command Injection
Source CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 3 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by fedora
, 28 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 14 minutes after disclosure
First Exploit-DB entry (opens in a new tab)
Fedora - Local Privilege Escalation
, 147 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
1. Immediately restrict local user access to systems running vulnerable ABRT daemon versions to trusted personnel only. 2. Disable or uninstall the ABRT daemon if crash reporting is not essential, reducing the attack surface. 3. Monitor and audit local user activities for suspicious command injection attempts or abnormal ABRT behavior. 4. Apply vendor patches as soon as they become available; track Fedora security advisories for updates. 5. Implement mandatory access controls (e.g., SELinux, AppArmor) to confine ABRT daemon privileges and prevent unauthorized command execution. 6. Employ input validation and sanitization in any custom scripts or tools interacting with ABRT or Docker commands. 7. Use container security best practices to limit Docker command exposure and isolate container management processes. 8. Conduct regular vulnerability assessments and penetration testing focusing on local privilege escalation vectors. These steps go beyond generic advice by emphasizing access restriction, daemon confinement, and proactive monitoring until patches are deployed.
Description
A flaw was found in the ABRT daemon’s handling of user-supplied mount information.ABRT copies up to 12 characters from an untrusted input and places them directly into a shell command (docker inspect %s) without proper validation. An unprivileged local user can craft a payload that injects shell metacharacters, causing the root-running ABRT process to execute attacker-controlled commands and ultimately gain full root privileges.