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-2026-68509
MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-117875 (ENISA EUVD)Source: ENISA EUVD
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.3
- EG Score
- 6.3MEDIUMmedium confidence
- EG Risk
- 28EG Risk 28/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity63% × 45%Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 3rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 5, 2026
Last Modified
November 12, 2026
Advisory Details (3)
Auto-updated Nov 10, 2026Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)
Path traversal in shared attachment handling can write files outside the intended shared directory · Advisory · M66B/FairEmail · GitHub
https://github.com/M66B/FairEmail/security/advisories/GHSA-w92m-2v27-mvg9GitHub release Patch Available
1.2325 Elopteryx *
Patch available: M66B/FairEmail 1.2325
https://github.com/M66B/FairEmail/releases/tag/1.2325GitHub commit Patch Available
commit 538523dded74 (M66B/FairEmail)
Patch available: M66B/FairEmail 1.2325 (contains commit 538523dded74)
https://github.com/M66B/FairEmail/commit/538523dded741f7a8a76052de9a69806d357c0f4Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 9× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 22:30 UTCEchelonGraph re-scored
- 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-10 05:27 UTCEchelonGraph re-scored
- 2026-11-10 04:55 UTCEchelonGraph re-scored
- 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-06 00:04 UTCENISA EUVD ID recordedEUVD-2026-117875 · Source: ENISA EUVD
- 2026-11-05 23:28 UTCEchelonGraph re-scored
- 2026-11-05 22:53 UTCEchelonGraph re-scoredFirst assessed: 6.3 MEDIUM
- 2026-11-05 22:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-68509?
CVE-2026-68509 is a medium-severity vulnerability; its CVE record was published on November 5, 2026. 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…
When was the CVE record for CVE-2026-68509 published?
The CVE record for CVE-2026-68509 was published on November 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-68509 actively exploited?
CVE-2026-68509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68509?
CVE-2026-68509 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68509?
A fix for CVE-2026-68509 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-68509
Is Your Infrastructure Affected by CVE-2026-68509?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.