Privilege escalation in Google Android
CVE-2025-48613
In VBMeta, there is a possible way to modify and resign VBMeta using a test key, assuming the original image was previously signed with the same key. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Vulnerability class: Privilege Escalation
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.4th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 0th percentile — 0.4% 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 Android SoC
Weakness classification (CWE)
References
- source.android.com/docs/security/bulletin/2026/2026-03-01 (vendor-advisory)
Frequently asked questions
- What is CVE-2025-48613?
- CVE-2025-48613 is a high-severity vulnerability in Google Android, classified under Improper Privilege Management. CVSS score: 7.8/10. Published 2026-03-02.
- How severe is CVE-2025-48613?
- High severity. CVSS v3 base score is 7.8 out of 10.