apport: Arbitrary file creation or overwrite via path traversal in base64-encoded problem report keys
- 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? →
- 16/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, a crash-report tool, is affected by a path traversal flaw in how it handles base64-encoded keys in problem reports. A local attacker who supplies a crafted crash report, and gets a user to process it with apport-unpack, can create or overwrite files outside the intended directory, such as shell startup files like .bashrc, which could allow code execution in that user's context.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In apport before 2.37.0, a path traversal vulnerability allows an attacker who can supply a crafted crash report to cause unintended file creation or overwrite outside the intended extraction directory when the report is processed with apport-unpack.
The key-name validation added for CVE-2026-77113 does not cover base64-encoded keys skipped by ProblemReport.load(binary=False), and ProblemReport.extract_keys() writes them to a file path built from the key without validation. This allows an attacker to create or overwrite arbitrary files writable by the invoking user, such as .bashrc or .profile, gaining persistence or code execution in that user's context.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Shipped in major Linux distributions
- Severity5.7/10CVSS 5.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 38 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.16.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-86692
Is CVE-2026-86692 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-86692?
apport: from 2.16.0 before 2.37.0.Source: cve.now feed data
How do I fix CVE-2026-86692?
Upgrade to a fixed version: 2.37.0.Source: cve.now feed data