AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 48 Bitcoin

config: don't save "hidden wallet" paths in CURRENT_WALLET cv

Public commit record

What the developer wrote

Authored by SomberNight

85/100 · Strong
config: don't save "hidden wallet" paths in CURRENT_WALLET cv

otherwise if the android app is launched and the last opened wallet was a hidden wallet, it would get automatically opened

similarly, don't add it into the recents list (though that's not exposed in qml atm)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit fixes a privacy leak in the Electrum wallet app. Previously, if a user opened a 'hidden wallet' (one whose filename starts with a dot, like a secret file), Electrum would remember it as the last-used wallet and could reopen it automatically on Android startup. It would also appear in the recent wallets list. The change makes Electrum forget these hidden wallets so they don't resurface automatically or show up in recents, protecting the user's choice to keep them discreet.

Recommended action

Users who rely on hidden wallets should upgrade to a version containing this commit, especially on Android. Review whether any existing config files already contain hidden wallet paths in `current_wallet` or recent files and clear them if desired. No immediate active-exploitation response is required; this is a defense-in-depth/privacy hardening fix.

Security signals we found

01

Privacy leak: hidden wallet filename persisted in config and could be auto-reopened

02

Information disclosure: hidden wallet path exposed in recently-opened list

03

Behavioral fix: setter silently drops sensitive value rather than persisting it

04

Android-specific impact: automatic reopening at app launch increases exposure

Risk score

Why this scored 48/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 10/15
Affected reach 7/15
Confidence 7/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.