Lock-screen bypass via unauthenticated protected-package modification
Published Sep 4, 2025 · Updated Feb 26, 2026
Authentication bypass in the System component of Google Cloud Android 13 through 15 allows local users to access a locked device. The Settings app permits protected packages to be disabled, force-stopped, or stripped of updates without first requiring biometric or lock-screen authentication. Physical access to a locked device is required; exploitation needs no execution privileges or user interaction and exposes only limited device data.
Summary
What happened
Authentication bypass in the System component of Google Cloud Android 13 through 15 allows local users to access a locked device. The Settings app permits protected packages to be disabled, force-stopped, or stripped of updates without first requiring biometric or lock-screen authentication. Physical access to a locked device is required; exploitation needs no execution privileges or user interaction and exposes only limited device data.
The record
- CVE
- CVE-2025-26421
- Published
- Sep 4, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-290, T1461
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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=13
- Affected versionversion=14
- Affected versionversion=15
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.
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