CVE-2026-68509: M66B FairEmail · Path Traversal
Affects M66B FairEmailSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.2325 when convenient.
Data as of 5 Nov 2026, 23:05 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.3 |
|---|
- Patch
- Available – fixed in 1.2325
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade M66B FairEmail to 1.2325.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| M66BFairEmail | Affected
| Fixed in
|
AI-suggested
Upgrade FairEmail to version 1.2325 or later, where this path traversal vulnerability is fixed. No additional mitigations are required as the fix addresses the root cause.
Description
CVE-2026-68509 is a path traversal vulnerability in the FairEmail Android app prior to version 1.2325. The flaw allows a local attacker-controlled app to supply crafted filenames that escape the intended shared attachment directory and overwrite or corrupt files in FairEmail's private data directory, including sensitive account or message databases. Exploitation requires the FairEmail app to be locked with PIN or biometric authentication and user interaction to unlock it. The issue is fixed in version 1.2325.