PatchSiren cyber security CVE debrief
CVE-2026-116071 rotki CVE debrief
CVE-2026-116071 is a high-severity vulnerability in rotki, a cryptocurrency portfolio tracking application, affecting versions before 1.44.2. The vulnerability stems from a weak key derivation mechanism used for encrypting premium cloud backups. Specifically, the premium sync key is generated as a single unsalted SHA-256 hash of the user's password. This weakness allows attackers who obtain an uploaded backup blob to perform GPU-parallel offline password guessing attacks, potentially decrypting the database. The database contains sensitive information such as exchange API keys, secrets, wallet addresses, and transaction history.
- Vendor
- rotki
- Product
- Unknown
- CVSS
- HIGH 8.2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-25
- Original CVE updated
- 2026-10-25
- Advisory published
- 2026-10-25
- Advisory updated
- 2026-10-25
Who should care
Defenders responsible for cryptocurrency portfolio management applications, specifically those using rotki's premium cloud backup features, should assess their exposure and take immediate action to secure their installations.
Why it matters
CVE-2026-116071 is a high-severity vulnerability in rotki that allows attackers to brute-force backups due to weak key derivation. Defenders should verify exposure, assess security, and prioritize upgrading to version 1.44.2 or later.
- GPU-parallel offline password guessing attacks can be performed by attackers who obtain a backup blob.
- Decrypting the database containing exchange API keys, secrets, wallet addresses, and transaction history is potentially possible.
- Secure password practices and protection of backup files are crucial to mitigating this vulnerability.
- Verification of exposure and security of rotki installations is required.
Technical summary
The vulnerability in rotki versions before 1.44.2 is caused by a weak key derivation mechanism for premium cloud backups. The premium sync key is generated as a single unsalted SHA-256 hash of the user's password, making it susceptible to GPU-parallel offline password guessing attacks. Attackers who obtain a backup blob can potentially decrypt the database containing sensitive information such as exchange API keys, secrets, wallet addresses, and transaction history. This vulnerability allows attackers to brute-force backups due to weak key derivation, enabling GPU-parallel offline password guessing attacks. Defenders should verify exposure, assess security, and prioritize upgrading to version 1.44.2 or later.
Defensive priority
Defenders should prioritize verifying exposure and assessing the security of their rotki installations, especially if they use premium cloud backup features. Immediate action is required to upgrade to version 1.44.2 or later and to educate users about secure password practices and the importance of protecting backup files.
Recommended defensive actions
- Verify if the rotki installation is using premium cloud backup features and assess the exposure to potential attacks.
- Upgrade to rotki version 1.44.2 or later to address the weak key derivation vulnerability.
- Educate users about the importance of using strong, unique passwords and protecting backup files.
- Consider implementing additional security measures such as multi-factor authentication for accessing sensitive data.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and associated references provide details about the vulnerability, its impact, and potential mitigations. However, the corpus does not establish definitive exploitation or victim data. Key sources include the CVE Program, NVD, and various GitHub references related to rotki.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-116071 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-116071
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-116071 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-116071
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/rotki/rotki
-
Source reference
Unverified legacy reference
URL: https://github.com/rotki/rotki/blob/v1.44.1/rotkehlchen/crypto.py
-
Source reference
Unverified legacy reference
URL: https://github.com/rotki/rotki/blob/v1.44.1/rotkehlchen/data_handler.py
-
Source reference
Unverified legacy reference
URL: https://github.com/rotki/rotki/issues/13393
-
Source reference
Unverified legacy reference
URL: https://github.com/rotki/rotki/pull/13401
-
Source reference
Unverified legacy reference
URL: https://github.com/rotki/rotki/releases/tag/v1.44.2
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/rotki-before-1.44.2-weak-key-derivation-for-premium-cloud-backup-encryption
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.