CVE-2025-52294
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient validation of the screen lock mechanism in Trust Wallet v8.45 allows physically proximate attackers to bypass the lock screen and view the wallet balance.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceTrust Wallet v8.45 has insufficient validation in its screen lock mechanism, allowing a physically proximate attacker to bypass the lock screen and access the app to view the wallet balance. The vulnerability stems from a flaw in how the app validates lock state before displaying sensitive financial information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Trust Wallet versionOpen Trust Wallet app, go to Settings (gear icon) > About or Wallet Settings > version number. Alternatively, check in Play Store (Android) or App Store (iOS) under app information.Affected if Version is 8.45 (the affected version)
-
Confirm screen lock is enabledIn Trust Wallet, navigate to Settings > Security or Privacy > Screen Lock. Verify if a lock method (PIN, biometric, or password) is set and enabled.Affected if Screen lock is enabled and version is 8.45 (the vulnerability allows bypass even when lock is active)
-
Test lock screen bypassLock the app by pressing home button or switching apps while screen lock is enabled. Then reopen Trust Wallet and observe whether it immediately displays the wallet balance and main interface without prompting for authentication.Affected if The app displays wallet balance or financial data without requesting authentication (indicating the lock bypass is present)
-
Verify sensitive data visibilityAfter performing step 3, check if wallet addresses, balances, transaction history, or other financial details are visible on the main screen without entering a PIN, password, or biometric.Affected if Sensitive wallet data is visible without any authentication prompt
User is affected if Trust Wallet version 8.45 is installed and the app displays wallet balances or sensitive financial information without requiring authentication after being locked.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUsers should update to a patched version of Trust Wallet when released. The fix requires implementing proper validation of the screen lock state before allowing access to wallet balances and sensitive data.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52294 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52294 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data