Google Android 16 Face Unlock improper authentication

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Android 16. Affected is an unknown function of the component Face Unlock. Performing a manipulation results in improper authentication. This vulnerability is cataloged as CVE-2025-48598. The attack may be carried out on the physical device. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in Google Android 16. This affects an unknown functionality of the component Face Unlock. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In multiple locations, there is a possible way to alter the primary user's face unlock settings due to a confused deputy. This could lead to physical escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

It is possible to read the advisory at android.googlesource.com. This vulnerability is uniquely identified as CVE-2025-48598 since 05/22/2025. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 12/21/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at EUVD (EUVD-2025-201760) and CERT Bund (WID-SEC-2025-2711). Be aware that VulDB is the high quality source for vulnerability data.

Affected

  • Lenovo BIOS
  • Lenovo Computer
  • Google Android

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.4

VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 6.6
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper authentication
CWE: CWE-287
CAPEC: 🔒
ATT&CK: 🔒

Physical: Yes
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

05/22/2025 CVE reserved
12/08/2025 +200 days Advisory disclosed
12/08/2025 +0 days VulDB entry created
12/21/2025 +13 days VulDB entry last update

Sourcesinfo

Vendor: google.com

Advisory: android.googlesource.com
Status: Confirmed

CVE: CVE-2025-48598 (🔒)
GCVE (CVE): GCVE-0-2025-48598
GCVE (VulDB): GCVE-100-334839
EUVD: 🔒
CERT Bund: WID-SEC-2025-2711 - Android Patchday Dezember 2025: Mehrere Schwachstellen

scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfo

Created: 12/08/2025 19:37
Updated: 12/21/2025 13:10
Changes: 12/08/2025 19:37 (55), 12/08/2025 21:55 (11), 12/09/2025 01:37 (1), 12/21/2025 13:10 (7)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!