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.
Published:
2026-11-10
Score:
n/a
EPSS:
n/a
KEV:
No
Impact:
n/a
Action:
n/a
Analysis
No analysis available yet.
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 available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
History
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 |
|
Subscriptions
No data.
MITRE
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-11-10T19:22:10.871Z
Reserved: 2026-07-06T06:25:53.894Z
Link: CVE-2026-59596
Vulnrichment
No data.
NVD
Status : Received
Published: 2026-11-10T20:19:30.227
Modified: 2026-11-10T20:19:30.227
Link: CVE-2026-59596
Redhat
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.