FairEmail: Path traversal in shared attachment handling can write files outside the intended shared directory
- Exploited
- No known exploitation
- Fix
- Fixed in 1.2325
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.2325.
- 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? →
- 6/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
FairEmail, an open source Android email app, has a path traversal flaw in how it handles shared attachments, which lets a malicious app on the same device overwrite or corrupt files in FairEmail's private data, including account and message databases. The attack is local, needs no login, and requires the user to unlock FairEmail, and it only works when app lock with a PIN or biometric is enabled.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
FairEmail is a fully featured, open source, privacy-friendly email app for Android. Prior to 1.2325, shared attachment handling does not adequately sanitize an attacker-controlled filename before constructing its destination path. A local attacker-controlled app can therefore supply path components that escape the intended shared attachment directory and overwrite or corrupt files in the FairEmail private data directory, including account or message databases. Exploitation requires app lock using PIN or biometric authentication and user interaction to unlock FairEmail. This issue is fixed in version 1.2325.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.2325.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- M66B FairEmail
fixed in 1.2325
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-68509
Is CVE-2026-68509 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-68509?
FairEmail: before 1.2325.Source: cve.now feed data
How do I fix CVE-2026-68509?
Upgrade to a fixed version: 1.2325.Source: cve.now feed data