CVE-2025-32321: High severity Google Android vulnerability
Published Sep 2, 2025
·Updated
In isSafeIntent of AccountTypePreferenceLoader.java, there is a possible way to bypass an intent type check due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Affected Software
5 affected components
Google Android
Google Android=13.0
Google Android=14.0
Google Android=15.0
Google Android=16.0
Remediation
Event History
Sep 2, 2025
CVE Published
via Android·12:00 AM
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software
Sep 4, 2025
CVE Published
via MITRE·06:33 PM
Data Sourced
via MITRE·06:33 PM
DescriptionWeakness
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-32321?
CVE-2025-32321 has a high severity rating due to its potential for local escalation of privilege.
2
How do I fix CVE-2025-32321?
To fix CVE-2025-32321, update your Android device to version 16.0 or later that addresses the vulnerability.
3
Which versions of Android are affected by CVE-2025-32321?
CVE-2025-32321 affects Android versions 13.0, 14.0, and 15.0.
4
Can CVE-2025-32321 be exploited without user interaction?
Yes, CVE-2025-32321 can be exploited without any user interaction required.
5
What component is involved in CVE-2025-32321?
CVE-2025-32321 involves the isSafeIntent method in AccountTypePreferenceLoader.java.