CVE-2026-102539

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th 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
Elevated

Also known asEUVD-2026-97964 (ENISA EUVD)Source: ENISA EUVD

5.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Super Productivity is an advanced todo list app with integrated timeboxing and time tracking capabilities. From 17.3.0 until 18.13.1, the SuperSync end-to-end encryption setup calls sync(true) before a user sets an encryption password, causing the operation-upload path to transmit and store all user operations in plaintext. The exposed operations can include private task content and connected issue-provider credentials, including reusable passwords, API tokens, and app passwords. Users who complete E2EE setup have the plaintext operations deleted, while users who leave the password-setting step can leave the data stored indefinitely. The Disable SuperSync action did not remove plaintext that had already been uploaded. Routing and causal metadata remain plaintext by design and are not part of this vulnerability. This issue is fixed in version 18.13.1.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
42
EG Risk 42/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)
Severity57% × 45%
Impact severity (EG Severity): CVSS 5.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.2%
EPSS %ILE
5th
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 (5.7): severity, escalated by confirmed exploitation. This CVE's 5.7 is its impact severity (EG Severity), not escalated.

EG Severity
5.7 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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (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

October 12, 2026

Last Modified

October 16, 2026

Advisory Details (4)

Auto-updated Oct 12, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

SuperSync E2EE setup uploads and stores all user operations in plaintext before password is set · Advisory · super-productivity/super-productivity · GitHub

Affected: v18.13.1.

https://github.com/super-productivity/super-productivity/security/advisories/GHSA-9v8x-68pf-p5x7
GitHub release Patch Available

v18.13.1

Patch available: super-productivity/super-productivity v18.13.1

https://github.com/super-productivity/super-productivity/releases/tag/v18.13.1
GitHub pull request

fix(sync): never transmit plaintext operations for E2EE-mandatory providers

Fix merged in super-productivity/super-productivity PR #8670 on 2026-07-01 — awaiting tagged release

https://github.com/super-productivity/super-productivity/pull/8670
GitHub commit

commit 63253f8e0c3b (super-productivity/super-productivity)

Fix landed in super-productivity/super-productivity commit 63253f8e0c3b — awaiting tagged release

https://github.com/super-productivity/super-productivity/commit/63253f8e0c3b145f2d47f819ab8f910d6873fd88

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 30× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-29 14:49 UTCEG score recompute
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-25 14:56 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-23 09:28 UTCEG score recompute
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-18 05:10 UTCEG score recompute
  20. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-16 20:13 UTCEG score recompute
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-15 14:28 UTCEG score recompute
  25. 2026-10-15 14:03 UTCEG score recompute
Show 5 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-12 22:28 UTCEG score recompute
  4. 2026-10-12 21:30 UTCEG score recomputeFirst assessed: 5.7 MEDIUM
  5. 2026-10-12 21:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102539?
CVE-2026-102539 is a medium-severity vulnerability; its CVE record was published on October 12, 2026. Super Productivity is an advanced todo list app with integrated timeboxing and time tracking capabilities. From 17.3.0 until 18.13.1, the SuperSync end-to-end encryption setup calls sync(true) before a user sets an encryption password, causing the operation-upload path to transmit and store all…
When was the CVE record for CVE-2026-102539 published?
The CVE record for CVE-2026-102539 was published on October 12, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-102539 actively exploited?
CVE-2026-102539 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102539?
CVE-2026-102539 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102539?
A fix for CVE-2026-102539 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-102539

Explore →

Is Your Infrastructure Affected by CVE-2026-102539?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs