Vulnerability in Google Android
CVE-2025-32347
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.001 (0.3th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 0th percentile — 0.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.001 · newest: 0.001 · change: +0.000
Affected products
- Google Android — versions 15.0, 14.0, 13
Weakness classification (CWE)
Public proof-of-concept exploits
References
- android.googlesource.com/platform/packages/apps/Settings/+/25cfacbe5ac2423b8fe1… (Product, Patch)
- source.android.com/security/bulletin/2025-09-01 (Vendor Advisory)
Frequently asked questions
- What is CVE-2025-32347?
- CVE-2025-32347 is a high-severity vulnerability in Google Android, classified under CWE-926. CVSS score: 7.8/10. Published 2025-09-04.
- How severe is CVE-2025-32347?
- High severity. CVSS v3 base score is 7.8 out of 10.
- Is CVE-2025-32347 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.