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
|
Fri, 13 Nov 2026 22:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Security Coprocessor Default Value in Android mpu.c |
Fri, 13 Nov 2026 13:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
Thu, 12 Nov 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-453 | |
| Metrics |
cvssV3_1
|
Thu, 12 Nov 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Security Coprocessor Execution from Non‑Secure Memory | |
| Weaknesses | CWE-284 CWE-665 |
Thu, 12 Nov 2026 03:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Security Coprocessor Execution from Non‑Secure Memory | |
| Weaknesses | CWE-284 CWE-665 |
Tue, 10 Nov 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In multiple functions of mpu.c, there is a possible way to execute code from non-secure memory in the security coprocessor due to an insecure default value. 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.
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-11-13T05:01:34.798Z
Reserved: 2026-07-06T06:25:53.894Z
Link: CVE-2026-59596
Updated: 2026-11-12T19:30:54.779Z
Status : Awaiting Analysis
Published: 2026-11-10T20:19:30.227
Modified: 2026-11-13T05:18:50.410
Link: CVE-2026-59596
No data.
OpenCVE Enrichment
Updated: 2026-11-13T21:45:09Z