CVE-2025-26428 json
In startLockTaskMode of LockTaskController.java, there is a possible lock screen bypass due to a logic error in the code.
published last yr. modified 4mo ago also EUVD-2025-26854
- cvss
- 3.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
In startLockTaskMode of LockTaskController.java, there is a possible lock screen bypass due to a logic error in the code. This could lead to physical escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
Patch / fix
Is CVE-2025-26428 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 3.2 | CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 3.2 | CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
Affected products
- Google Android
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
References
Sources
- CVE List CVE-2025-26428
- NVD CVE-2025-26428
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.