CVE-2025-26428
In startLockTaskMode of LockTaskController.java, there is a possible lock screen bypass due to a...
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.
Attack profile
How easy it is to exploit
- Attack vector
- Physical
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
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.
- Record
CVE-2025-26428- CVSS 3.1
- 3.2 Low
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N - Weakness
- CWE-290
- Updated
- 2026-11-02
EUVDEUVD-2025-26854
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.
- Record
EUVD-2025-26854- CVSS 3.1
- 3.2 Low
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-8r65-jwf6-5j33
In startLockTaskMode of LockTaskController.java, there is a possible lock screen bypass due to a...
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.
- Record
GHSA-8r65-jwf6-5j33- CVSS 3.1
- 3.2 Low
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N - Weakness
- CWE-290
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2025-26428- CVSS 3.1
- 3.2 Low
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N - Weakness
- CWE-290
- Updated
- 2026-11-02
OSVASB-A-378514614 No score
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.
- Record
ASB-A-378514614- Updated
- 2026-11-10
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
platform/frameworks/baseAndroid |
15-next:0 up to 15-next:2025-05-01, plus listed versions 15-next |
15-next:2025-05-01 |
platform/frameworks/baseAndroid |
15:0 up to 15:2025-05-01, plus listed versions 15 |
15:2025-05-01 |
platform/frameworks/baseAndroid |
13:0 up to 13:2025-05-01, plus listed versions 13 |
13:2025-05-01 |
platform/frameworks/baseAndroid |
14:0 up to 14:2025-05-01, plus listed versions 14 |
14:2025-05-01 |
History
| Recorded | Changed | Sources |
|---|---|---|
| facts | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-26428 is a low vulnerability (CVSS 3.2) in Google Android, published May 1, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.10%, the 1st percentile. Fixed in platform/frameworks/base 15-next:2025-05-01.