7.7
HIGH CVSS 3.1
CVE-2026-0017
Apache BiometricService Fingerprint Unlock Privilege Escalation
Description

In onChange of BiometricService.java, there is a possible way to enable fingerprint unlock due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

INFO

Published Date :

March 2, 2026, 7:16 p.m.

Last Modified :

March 6, 2026, 4:16 a.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-0017 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Google android
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 3.1 HIGH [email protected]
Solution
Fix logic error in BiometricService.java to prevent unauthorized fingerprint unlock enablement.
  • Review and correct the logic in BiometricService.java.
  • Implement proper authorization checks for fingerprint unlock.
  • Test the fix to ensure security.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-0017.

URL Resource
https://source.android.com/docs/security/bulletin/2026/2026-03-01
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-0017 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-0017 weaknesses.

CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs Accessing Functionality Not Properly Constrained by ACLs CAPEC-5: Blue Boxing Blue Boxing CAPEC-13: Subverting Environment Variable Values Subverting Environment Variable Values CAPEC-17: Using Malicious Files Using Malicious Files CAPEC-39: Manipulating Opaque Client-based Data Tokens Manipulating Opaque Client-based Data Tokens CAPEC-45: Buffer Overflow via Symbolic Links Buffer Overflow via Symbolic Links CAPEC-51: Poison Web Service Registry Poison Web Service Registry CAPEC-59: Session Credential Falsification through Prediction Session Credential Falsification through Prediction CAPEC-60: Reusing Session IDs (aka Session Replay) Reusing Session IDs (aka Session Replay) CAPEC-76: Manipulating Web Input to File System Calls Manipulating Web Input to File System Calls CAPEC-77: Manipulating User-Controlled Variables Manipulating User-Controlled Variables CAPEC-87: Forceful Browsing Forceful Browsing CAPEC-104: Cross Zone Scripting Cross Zone Scripting CAPEC-127: Directory Indexing Directory Indexing CAPEC-402: Bypassing ATA Password Security Bypassing ATA Password Security CAPEC-647: Collect Data from Registries Collect Data from Registries CAPEC-668: Key Negotiation of Bluetooth Attack (KNOB) Key Negotiation of Bluetooth Attack (KNOB) CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs Accessing Functionality Not Properly Constrained by ACLs CAPEC-17: Using Malicious Files Using Malicious Files CAPEC-20: Encryption Brute Forcing Encryption Brute Forcing CAPEC-22: Exploiting Trust in Client Exploiting Trust in Client CAPEC-36: Using Unpublished Interfaces or Functionality Using Unpublished Interfaces or Functionality CAPEC-51: Poison Web Service Registry Poison Web Service Registry CAPEC-57: Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Utilizing REST's Trust in the System Resource to Obtain Sensitive Data CAPEC-59: Session Credential Falsification through Prediction Session Credential Falsification through Prediction CAPEC-65: Sniff Application Code Sniff Application Code CAPEC-74: Manipulating State Manipulating State CAPEC-87: Forceful Browsing Forceful Browsing CAPEC-107: Cross Site Tracing Cross Site Tracing CAPEC-127: Directory Indexing Directory Indexing CAPEC-237: Escaping a Sandbox by Calling Code in Another Language Escaping a Sandbox by Calling Code in Another Language CAPEC-477: Signature Spoofing by Mixing Signed and Unsigned Content Signature Spoofing by Mixing Signed and Unsigned Content CAPEC-480: Escaping Virtualization Escaping Virtualization CAPEC-668: Key Negotiation of Bluetooth Attack (KNOB) Key Negotiation of Bluetooth Attack (KNOB)

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-0017 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-0017 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by [email protected]

    Mar. 06, 2026

    Action Type Old Value New Value
    Added Reference https://source.android.com/docs/security/bulletin/2026/2026-03-01
    Removed Reference https://source.android.com/security/bulletin/2026-03-01
    Removed Reference Type https://source.android.com/security/bulletin/2026-03-01 Types: Broken Link
  • Reanalysis by [email protected]

    Mar. 03, 2026

    Action Type Old Value New Value
    Changed CPE Configuration OR *cpe:2.3:o:google:android:16.0:qpr2:*:*:*:*:*:* *cpe:2.3:o:google:android:16.0:-:*:*:*:*:*:* OR *cpe:2.3:o:google:android:16.0:-:*:*:*:*:*:* *cpe:2.3:o:google:android:16.0:qpr2_beta_1:*:*:*:*:*:* *cpe:2.3:o:google:android:16.0:qpr2_beta_2:*:*:*:*:*:* *cpe:2.3:o:google:android:16.0:qpr2_beta_3:*:*:*:*:*:*
  • Initial Analysis by [email protected]

    Mar. 03, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
    Added CPE Configuration OR *cpe:2.3:o:google:android:16.0:qpr2:*:*:*:*:*:* *cpe:2.3:o:google:android:16.0:-:*:*:*:*:*:*
    Added Reference Type Android (associated with Google Inc. or Open Handset Alliance): https://source.android.com/security/bulletin/2026-03-01 Types: Broken Link
  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Mar. 03, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
    Added CWE CWE-285
    Added CWE CWE-693
  • New CVE Received by [email protected]

    Mar. 02, 2026

    Action Type Old Value New Value
    Added Description In onChange of BiometricService.java, there is a possible way to enable fingerprint unlock due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
    Added Reference https://source.android.com/security/bulletin/2026-03-01
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.