EUVD-2025-210013
GHSA-2mvq-m5m5-v7m7
Severity by source
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
In multiple locations, there is a possible way to achieve code execution due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
AnalysisAI
Local privilege escalation in Google Android (versions 14, 15, 16, and 16-qpr2) stems from an integer overflow (CWE-190) that can be triggered without user interaction to achieve code execution. With CVSS 8.4 and SSVC technical impact rated 'total,' a local attacker on the device can elevate privileges across security boundaries without additional execution rights. No public exploit identified at time of analysis and SSVC reports exploitation status as 'none.'
Technical ContextAI
The flaw is an integer overflow (CWE-190) affecting Android per CPE cpe:2.3:a:google:android, reported in multiple code locations within the Android platform. Integer overflows typically arise when an arithmetic operation produces a value outside the representable range of the integer type, leading to undersized buffer allocations, incorrect length checks, or out-of-bounds memory operations - any of which can be leveraged into memory corruption and subsequent code execution. Because Android relies on layered sandboxing (app UID isolation, SELinux, Mainline modules), an overflow that enables code execution in a privileged process can break out of an application sandbox into a higher-privilege context.
RemediationAI
Apply the Android Security Bulletin updates referenced at https://source.android.com/docs/security/bulletin/2026/2026-06-01; devices should be updated to a security patch level of 2026-06-01 or later as published by Google and downstream OEMs. Exact fix versions were not enumerated in the provided data - patch available per vendor advisory. Until OEM/carrier updates are delivered, compensating controls include restricting app installs to Google Play with Play Protect enabled, blocking sideloading via MDM, prohibiting installation of untrusted APKs on managed fleets, and prioritizing patches on devices with sensitive data; the trade-off of MDM-based sideload restrictions is reduced flexibility for developers and power users.
Share
External POC / Exploit Code
Leaving vuln.today