Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 06 Nov 2026 01:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
M66b
M66b fairemail |
|
| Vendors & Products |
M66b
M66b fairemail |
Thu, 05 Nov 2026 23:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | FairEmail: Path traversal in shared attachment handling can write files outside the intended shared directory | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-05T22:45:24.203Z
Reserved: 2026-07-30T16:19:08.081Z
Link: CVE-2026-68509
No data.
Status : Received
Published: 2026-11-05T23:16:56.587
Modified: 2026-11-05T23:16:56.587
Link: CVE-2026-68509
No data.
OpenCVE Enrichment
Updated: 2026-11-06T01:00:16Z