{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102539 exists.","fix":"No fix has been published for CVE-2026-102539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102539 is a medium-severity vulnerability in super-productivity, published on 12 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-102539 and fix it if it is affected.\n\nWhat it is: CVE-2026-102539 is a medium-severity vulnerability in super-productivity, published on 12 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102539 exists.\n\nAffected product: super-productivity. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102539/ (Markdown: https://insights.sbomify.com/CVE-2026-102539/index.md)","id":"CVE-2026-102539","markdown":"https://insights.sbomify.com/CVE-2026-102539/index.md","name":"CVE-2026-102539","record":{"aliases":["GHSA-9v8x-68pf-p5x7"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Super Productivity app","requires_auth":"high_privilege","summary":"Super Productivity users enabling SuperSync may leak private tasks and credentials in plaintext before setting an encryption password.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"},{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Super Productivity: SuperSync E2EE setup uploads and stores all user operations in plaintext before password is set","id":"CVE-2026-102539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Improper verification of the source of a communication channel in FreeRTOS-Plus-TCP Router Advertisement handling","id":"CVE-2026-102551"},"packages":[],"prev":{"headline":"This CVE has been rejected because it was issued to a development-only issue with no affected distributed version identified.","id":"CVE-2026-102536"},"products":["super-productivity"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["super-productivity"]},"summary":"Super Productivity users enabling SuperSync may leak private tasks and credentials in plaintext before setting an encryption password.","url":"https://insights.sbomify.com/CVE-2026-102539/"}