CVE-2025-32347High· 7.8▾ TwilightIn onStart of BiometricEnrollIntroduction.java, there is a possible way to determine the device's location due to an unsafe PendingIntent. This could lead to local escalation of privilege with no additional execution privileges needed. U…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Last analysed / modified upstream
0.09%
In onStart of BiometricEnrollIntroduction.java, there is a possible way to determine the device's location due to an unsafe PendingIntent. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
android = 13.0android = 14.0android = 15.0android = 16.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2025-48559Medium· 5.5In multiple functions of AppOpsService.java, there is a possible add a large amount of app ops due to improper input validation
CVE-2025-48541High· 7.8In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user profiles due to improper input validation
CVE-2026-45528High· 7.3In getManageSpaceActivityIntent of StorageManagerService.java, there is a possible LaunchAnyWhere chain due to an unsafe PendingIntent
CVE-2025-20804Medium· 6.7In dpe, there is a possible memory corruption due to use after free
CVE-2025-20805Medium· 6.7In dpe, there is a possible memory corruption due to use after free
CVE-2025-20800High· 7.8In mminfra, there is a possible out of bounds write due to a missing bounds check