No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 16 Nov 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sat, 14 Nov 2026 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Android Image Processing Bounds Check Error Enables Physical Privilege Escalation |
Sat, 14 Nov 2026 06:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
Fri, 13 Nov 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-119 | |
| Metrics |
cvssV3_1
|
Thu, 12 Nov 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unvalidated Memory Zeroing in Android Image Handling Allows Privilege Escalation | |
| Weaknesses | CWE-119 CWE-120 |
Thu, 12 Nov 2026 03:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Unvalidated Memory Zeroing in Android Image Handling Allows Privilege Escalation | |
| Weaknesses | CWE-119 CWE-120 |
Tue, 10 Nov 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In multiple locations, there is a possible way to zero arbitrary secure memory via unvalidated image body addresses due to a missing bounds check. This could lead to physical escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-11-13T16:27:13.328Z
Reserved: 2026-07-02T05:52:23.114Z
Link: CVE-2026-58805
Updated: 2026-11-12T19:48:05.716Z
Status : Awaiting Analysis
Published: 2026-11-10T20:19:27.487
Modified: 2026-11-13T17:17:32.883
Link: CVE-2026-58805
No data.
OpenCVE Enrichment
Updated: 2026-11-14T23:15:02Z