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.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://source.android.com/security/bulletin/2026-03-01 |
|
History
Tue, 03 Mar 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| CPEs | cpe:2.3:o:google:android:-:*:*:*:*:*:*:* | |
| Vendors & Products |
Google
Google android |
Tue, 03 Mar 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-269 | |
| Metrics |
cvssV3_1
|
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 |
|
Status: PUBLISHED
Assigner: google_android
Published: 2026-03-02T18:42:15.702Z
Updated: 2026-03-03T15:23:58.659Z
Reserved: 2025-05-22T18:12:23.625Z
Link: CVE-2025-48613
Updated: 2026-03-03T15:23:51.126Z
Status : Analyzed
Published: 2026-03-02T19:16:27.160
Modified: 2026-03-03T18:13:20.170
Link: CVE-2025-48613
No data.