Session access via failed PIN logout cleanup
Published Mar 14, 2025 · Updated Mar 14, 2025
PIN lockout bypass in Element HQ Element Android 1.6.32 and earlier allows physically proximate attackers to keep guessing a user's PIN. After the failed-attempt limit, PinFragment requests credential clearing, but MainActivity treats a homeserver logout error as fatal and skips local cleanup. Physical possession of the device and a logout server error leave the Matrix session available for repeated PIN attempts and eventual access to its messages.
Summary
What happened
PIN lockout bypass in Element HQ Element Android 1.6.32 and earlier allows physically proximate attackers to keep guessing a user's PIN. After the failed-attempt limit, PinFragment requests credential clearing, but MainActivity treats a homeserver logout error as fatal and skips local cleanup. Physical possession of the device and a logout server error leave the Matrix session available for repeated PIN attempts and eventual access to its messages.
The record
- CVE
- CVE-2025-27606
- Published
- Mar 14, 2025
- Updated
- Mar 14, 2025
- Vendor
- Element HQ
- Product
- Element Android
- Classifications
- CWE-488, T1110.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 14, 2025CVE publishedPublication date reported by the CVE source.
- Mar 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.6.34
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo