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.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Android | unaffected |
|
No data.
No data.
No data.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
| Link | Providers |
|---|---|
| https://source.android.com/security/bulletin/2026-03-01 |
|
History
Mon, 02 Mar 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| References |
|
Projects
Sign in to view the affected projects.
MITRE
Status: PUBLISHED
Assigner: google_android
Published:
Updated: 2026-03-02T18:42:15.702Z
Reserved: 2025-05-22T18:12:23.625Z
Link: CVE-2025-48613
Vulnrichment
No data.
NVD
Status : Awaiting Analysis
Published: 2026-03-02T19:16:27.160
Modified: 2026-03-02T20:29:29.330
Link: CVE-2025-48613
Redhat
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.