CVE-2025-5467: Canonical apport · Incorrect Ownership Assignment
Affects Canonical apportSource CVE Database V5
Public exploit available · CVSS 1.9 Low.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 10 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntuubuntu/apportpkg:deb/ubuntu/apportOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-5467, organizations should first monitor Canonical’s official channels for patches or updates addressing the incorrect ownership assignment in Apport. Until patches are available, administrators can implement manual controls by auditing the ownership and permissions of crash report files generated by Apport, ensuring they conform to the principle of least privilege. This can be done by scripting periodic checks or using configuration management tools to enforce correct group ownership. Limiting local user privileges to only trusted personnel reduces the risk of exploitation. Additionally, organizations should consider disabling Apport on systems where crash reporting is not essential or redirecting crash reports to secure locations with restricted access. Implementing file system access controls (e.g., AppArmor or SELinux policies) can further restrict unauthorized access to crash files. Regular security training for system administrators about proper file permission management and monitoring for unusual access patterns can help detect potential misuse. Finally, integrating crash report handling into broader data protection and incident response policies ensures timely identification and remediation of any information disclosure.
Description
It was discovered that process_crash() in data/apport in Canonical's Apport crash reporting tool may create crash files with incorrect group ownership, possibly exposing crash information beyond expected or intended groups.