Local privilege escalation via reused VBMeta test key
Published Mar 2, 2026 · Updated Mar 2, 2026
Improper privilege management in Google Android SoC allows local users to gain elevated privileges by modifying and resigning VBMeta. VBMeta accepts a modified image re-signed with a test key when the original image was signed with that same key, preserving trust in attacker-altered metadata. Exploitation requires local low-privileged access and the original image's test-key condition; no user interaction is required, and successful abuse compromises the device.
Summary
What happened
Improper privilege management in Google Android SoC allows local users to gain elevated privileges by modifying and resigning VBMeta. VBMeta accepts a modified image re-signed with a test key when the original image was signed with that same key, preserving trust in attacker-altered metadata. Exploitation requires local low-privileged access and the original image's test-key condition; no user interaction is required, and successful abuse compromises the device.
The record
- CVE
- CVE-2025-48613
- Published
- Mar 2, 2026
- Updated
- Mar 2, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 2, 2026CVE publishedPublication date reported by the CVE source.
- Mar 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Android SoC
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo