CVE-2025-48577: Android Framework KeyguardViewMediator Lock Screen Bypass Vulnerability

platform/frameworks/base Updated 02 Mar 2026

Summary

01/03/2026
Yes i
High
Not published

CVE-2025-48577: In multiple functions of KeyguardViewMediator.java, there is a possible lockscreen bypass due to a race condition. Affects platform/frameworks/base across 4 version ranges.

>= 14:0, < 14:2026-03-01 >= 15:0, < 15:2026-03-01 >= 16:0, < 16:2026-03-01 >= 16-qpr2-next:0, < 16-qpr2-next:2026-03-01

Fixed in 16-qpr2-next:2026-03-01. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Android Framework is a set of libraries and tools that enable developers to create applications for the Android operating system. One of its key components is the KeyguardViewMediator, which manages the lock screen and user authentication processes. This component is crucial for ensuring that unauthorized users cannot access the device. However, a vulnerability has been identified that allows for a potential bypass of the lock screen, raising significant security concerns.

Vulnerability Detail

The vulnerability arises from a race condition in multiple functions of the KeyguardViewMediator.java file. This flaw allows an attacker to exploit the timing of operations to bypass the lock screen without requiring any user interaction or additional execution privileges. The implications of this vulnerability are severe, as it could lead to unauthorized access to sensitive information and local escalation of privileges.

How To Fix

Minimum fixed version

16-qpr2-next:2026-03-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can disable biometric authentication or lock screen features until the patch is applied. This can be done by navigating to Settings > Security > Screen lock and selecting 'None' or 'Swipe'. However, this is not a recommended long-term solution.

Conclusion

The CVE-2025-48577 vulnerability poses a significant risk to Android devices by allowing potential bypass of the lock screen. Users are strongly advised to update their systems to the patched version to mitigate this risk. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for platform/frameworks/base →

Share this vulnerability

FAQ

CVE-2025-48577 is a vulnerability in the Android Framework's KeyguardViewMediator that allows for a potential lock screen bypass due to a race condition.

This vulnerability can allow unauthorized users to bypass the lock screen, potentially gaining access to sensitive information stored on the device.

No, user interaction is not needed for exploitation, making it particularly dangerous.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.

As a temporary measure, consider disabling biometric authentication or lock screen features until the patch is applied.

Related vulnerabilities

Recent vulnerabilities recorded for platform/frameworks/base.

How To Fix

Minimum fixed version

16-qpr2-next:2026-03-01

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback