Every CVE Search/ Get API key

CVE-2025-48541

In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user...

7.8 HighFix available

In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user profiles due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
High
Availability
High

Exploit likelihood

0.09%Up 0.1 points since Sep 5, 2025
90%50%10%1%

What each source reports

CVE List Score used 7.8

In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user profiles due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
CVE-2025-48541
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-20
Updated
2026-11-02
EUVDEUVD-2025-26812 7.8

In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user profiles due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
EUVD-2025-26812
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
GitHub AdvisoriesGHSA-358v-5ppm-q7x9 7.8

In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user...

In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user profiles due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
GHSA-358v-5ppm-q7x9
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-20
Updated
2026-11-02
NVD 7.8

In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user profiles due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
CVE-2025-48541
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-20
Updated
2026-11-02
OSVASB-A-411418366 No score

In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user profiles due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
ASB-A-411418366
Updated
2026-11-05

Affected products

Affected packages

Affected packages
PackageAffectedFixed
platform/packages/apps/Settings
Android
16-next:0 up to 16-next:2025-09-01, plus listed versions
16-next
16-next:2025-09-01
platform/packages/apps/Settings
Android
15:0 up to 15:2025-09-01, plus listed versions
15
15:2025-09-01
platform/packages/apps/Settings
Android
16:0 up to 16:2025-09-01, plus listed versions
16
16:2025-09-01
platform/packages/apps/Settings
Android
13:0 up to 13:2025-09-01, plus listed versions
13
13:2025-09-01
platform/packages/apps/Settings
Android
14:0 up to 14:2025-09-01, plus listed versions
14
14:2025-09-01

History

History
RecordedChangedSources
factsOSV
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2025-48541 is a high vulnerability (CVSS 7.8) in Google Android, published September 1, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.09%, the 0th percentile. Fixed in platform/packages/apps/Settings 16-next:2025-09-01.

References

MoveEnter Open