Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-102539 Overview
CVE-2026-102539 affects Super Productivity, an open-source todo list application with integrated timeboxing and time tracking. The SuperSync end-to-end encryption (E2EE) setup flow calls sync(true) before the user establishes an encryption password. This behavior causes the operation-upload path to transmit and store user operations in plaintext on the sync server. Exposed data can include private task content and connected issue-provider credentials such as reusable passwords, API tokens, and application passwords. The flaw is tracked under [CWE-312: Cleartext Storage of Sensitive Information] and is fixed in version 18.13.1.
Critical Impact
Users who abandon the password-setting step may leave plaintext tasks and third-party provider credentials stored indefinitely on the sync server. The Disable SuperSync action does not purge data already uploaded.
Affected Products
- Super Productivity versions 17.3.0 through 18.13.0
- SuperSync provider in affected releases (providerMode = 'superSyncOps')
- Fixed in Super Productivity 18.13.1
Discovery Timeline
- 2026-10-12 - CVE-2026-102539 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-102539
Vulnerability Analysis
Super Productivity's SuperSync provider enforces E2EE for all synced operations. During initial provider configuration, the client invoked sync(true) before the user had chosen an encryption password. Without a usable key, the upload path serialized local operations and transmitted them to the server as cleartext. The server stored those operations until the user completed E2EE setup, at which point the plaintext records were deleted. Users who never completed setup left credentials and task content stored indefinitely. The vulnerability class is cleartext storage of sensitive information [CWE-312].
Root Cause
The OperationSyncCapable interface lacked a signal indicating that a provider mandates encryption. SuperSync had supportsOperationSync = true without any guard that distinguished mandatory E2EE from optional encryption. The upload routine therefore treated the first sync like any other, pushing operations before key material existed. Legitimate unencrypted providers (such as file-based sync) share the same code path, so a per-provider policy flag was required.
Attack Vector
Exposure occurs on the sync server storing uploaded operations. An operator with access to SuperSync backend storage, or an attacker who compromises that storage, can read uploaded plaintext records. The data includes private tasks and credentials for connected issue providers. The Disable SuperSync client action removed local configuration but did not call a server-side purge, so previously uploaded cleartext remained accessible.
// Patch: provider-types.ts — add isEncryptionMandatory signal
isEncryptionEnabled?(): Promise<boolean>;
+ /**
+ * Whether this provider mandates end-to-end encryption and must NEVER transmit
+ * plaintext operations. When true, the upload path refuses to push ops while no
+ * usable encryption key is configured yet (e.g. first-time setup, before the
+ * user has chosen a password): the encrypted snapshot uploaded by the
+ * encryption-enable flow becomes the first data to reach the server.
+ */
+ readonly isEncryptionMandatory?: boolean;
}
// Patch: super-sync.ts — opt SuperSync into mandatory E2EE
readonly maxConcurrentRequests = 10;
readonly supportsOperationSync = true;
readonly providerMode = 'superSyncOps' as const;
+ // SuperSync is E2EE-mandatory: the upload path must never push plaintext ops.
+ readonly isEncryptionMandatory = true;
Source: GitHub Commit 63253f8
Detection Methods for CVE-2026-102539
Indicators of Compromise
- Super Productivity installations running versions between 17.3.0 and 18.13.0 with SuperSync configured
- Server-side SuperSync storage containing operation records that lack ciphertext markers
- Issue-provider credentials (Jira, GitHub, GitLab tokens) appearing in sync payloads in readable form
- User accounts that initiated SuperSync setup but never completed the password step
Detection Strategies
- Inspect SuperSync server storage for operations that are not wrapped in the expected E2EE envelope.
- Audit client telemetry for upload events that occurred before the encryption-enable flow completed.
- Review integrations configured in Super Productivity and treat any associated API tokens, app passwords, and reusable credentials as exposed.
Monitoring Recommendations
- Log and alert on sync upload requests that occur prior to a successful key-establishment handshake.
- Monitor credential-use patterns for Jira, GitHub, GitLab, and other connected providers for anomalous access following SuperSync onboarding.
- Track Super Productivity client versions across the fleet and flag any instance still below 18.13.1.
How to Mitigate CVE-2026-102539
Immediate Actions Required
- Upgrade all Super Productivity clients to version 18.13.1 or later.
- Rotate every credential, API token, and app password used by SuperSync-connected issue providers.
- Request server-side deletion of SuperSync operation history for affected accounts, since Disable SuperSync does not remove previously uploaded plaintext.
- Complete the E2EE password step immediately on any new SuperSync setup to trigger plaintext cleanup.
Patch Information
The fix ships in Super Productivity 18.13.1. The patch introduces an isEncryptionMandatory flag on the OperationSyncCapable interface and sets it to true for the SuperSync provider. When the flag is set, the upload path refuses to transmit operations until a usable encryption key exists. Details are published in GitHub Security Advisory GHSA-9v8x-68pf-p5x7, Pull Request #8670, and Release v18.13.1.
Workarounds
- Disable SuperSync and switch to a local-only or file-based sync provider until the client is upgraded.
- If SuperSync must stay enabled, complete the encryption password setup in one session so plaintext operations are deleted.
- Remove connected issue-provider integrations before configuring SuperSync, and reconnect them only after E2EE is active.
# Verify installed Super Productivity version meets the fixed release
super-productivity --version
# Expected: 18.13.1 or later
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

