Deserialization in Google Android
CVE-2025-48535
- CVSS v3
- 7.8 High
- Public exploits
- None known
- EPSS
- 0.002 · 6.9th percentile
- Published
- 2025-09-04
In assertSafeToStartCustomActivity of AppRestrictionsFragment.java , there is a possible way to exploit a parcel mismatch resulting in a launch anywhere vulnerability due to unsafe deserialization. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Vulnerability class: Insecure Deserialization
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.
- Attack Vector
- Local
AV:L - Attack Complexity
- Low
AC:L - Privileges Required
- Low
PR:L - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- High
C:H - Integrity
- High
I:H - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.002, 6.9th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Google Android — versions 15.0, 14.0, 13
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (cxxsheng/cxxsheng). These reference the CVE in a list, notes or a scanner and are not exploit code for it.