rotki CVE-2026-116071: weak key for premium backups

None reported. No known exploitation stated.

Root cause: Per NVD/GHSA: 'the premium sync key is a single unsalted SHA-256 of the user password'; an attacker with an uploaded backup blob can run GPU-parallel offline guessing and decrypt a database 'containing exchange API keys, secrets, wallet addresses and transaction history.' Fixed in 1.44.2: Argon2id key derivation with AES-256-GCM (per rotki release notes).

Timeline, as sourced: Issue filed 19 Oct 2026; fix merged 19 Oct; v1.44.2 released 22 Oct; CVE published 25 Oct 2026 12:16 UTC (NVD); GHSA 12:30 UTC.

CVE-2026-116071 (opens in a new tab), published 25 October 2026, covers rotki, an open-source crypto portfolio tracker, before version 1.44.2. According to the record, the key protecting premium cloud backups was a single unsalted SHA-256 hash of the user's password. An attacker who obtains an uploaded backup could run fast, GPU-parallel offline password guessing and decrypt a database holding exchange API keys and secrets, wallet addresses and transaction history. The original report (opens in a new tab) notes that the local database already used 64,000 rounds of key derivation for the same password. rotki's 1.44.2 release (opens in a new tab), out 22 October, moves backups to Argon2id key derivation with AES-256-GCM. Older versions cannot read the new backups, so every syncing device needs the update. Users who suspect exposure should rotate exchange API keys.