Back to the CVE list
CVE-2026-68509

FairEmail: Path traversal in shared attachment handling can write files outside the intended shared directory

CVSS score

6.3

EPSS probability

—

Risk score

0.6

Published

3 h ago

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

FairEmail Path Traversal Vulnerability in Shared Attachment Handling

Sources read

2

Source agreement

Tam uyum

Evidence confidence

%63

Short explanation

A path traversal vulnerability exists in shared attachment handling in FairEmail prior to version 1.2325. A local attacker-controlled app can supply filenames to escape the intended shared directory and overwrite or corrupt files in the private data directory.

Why does it matter?

This vulnerability risks the integrity of critical private data such as account and message databases. It allows local attackers to perform unauthorized file overwrite operations.

What should be done?

  • Update FairEmail to version 1.2325
  • Follow vendor advisory guidance
Chain of evidence and sources3 verified claims

FairEmail 1.2325 öncesi sürümlerde, paylaşılan ek yönetimi saldırgan kontrollü dosya adlarını yeterince filtrelemez.

İstismar, PIN veya biyometrik kimlik doğrulaması kullanan uygulama kilidi ile kullanıcı etkileşimi gerektirir.

Bu zafiyet 1.2325 sürümünde giderilmiştir.

Show the technical text from the sources

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.

CVSS vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

CWE: CWE-22

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-68509 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1M66BFairEmail View
Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
6.3CVSS V3_1MEDIUMCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:HCVE CNA
6.3CVSS V31MEDIUMCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:HNVD

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-68509 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-68509 weaknesses.

Attack Vector and Accessibility

ExposureYerel erişim
PermissionsGerekmiyor
UserGerekiyor

Official Sources and Advisories

CVSS Vector Radar Chart

6.3 / 10
Attack VectorLocalComplexityHighPrivilegesNoneUser Interact.RequiredConfidentialityHighIntegrityHighAvailabilityHigh

Vulnerability Scoring Details

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
Attack VectorLocal
Attack ComplexityHigh
Privileges RequiredNone required
User Interaction—
Confidentiality (Gizlilik)High
Integrity (Bütünlük)High
Availability (Erişilebilirlik)High

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

M
M66B logo
M66B

Weakness Type (CWE & CAPEC)

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-68509"
CVE-2026-68509 · FairEmail: Path traversal in shared…