apport: Local privilege escalation to root via ldd execution on an attacker-controlled ExecutablePath in automatic crash report processing
- Exploited
- No known exploitation
- Fix
- Fixed in 2.37.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.37.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apport, the Ubuntu crash-reporting tool, has a local privilege escalation flaw that lets an unprivileged local user gain root on systems where automatic crash reporting is enabled. The attacker needs only low-privilege local access to plant a crafted crash file in /var/crash, and no user action is required.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In apport before 2.37.0, an improper privilege management vulnerability allows an unprivileged local attacker to gain root privileges on systems where automatic crash reporting is enabled. The automatic crash report processing pipeline runs as root and executes ldd on the attacker-controlled ExecutablePath field of a crash file placed in the world-writable /var/crash directory, causing the dynamic loader to load and execute an attacker-supplied audit module specified by the ELF's DT_AUDIT tag. This allows an attacker to execute arbitrary code with root privileges and fully compromise the affected system.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Shipped in major Linux distributions
- Severity7.3/10CVSS 7.3
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 39 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.37.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- apport
From 2.9.0 · fixed in 2.37.0
Evidence 3
- Patch
- Patch
- Report
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-84410
Is CVE-2026-84410 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-84410?
apport: from 2.9.0 before 2.37.0.Source: cve.now feed data
How do I fix CVE-2026-84410?
Upgrade to a fixed version: 2.37.0.Source: cve.now feed data