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.
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 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 |
|
Subscriptions
No data.
MITRE
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-11-10T19:21:47.762Z
Reserved: 2026-07-02T05:52:23.114Z
Link: CVE-2026-58805
Vulnrichment
No data.
NVD
Status : Awaiting Analysis
Published: 2026-11-10T20:19:27.487
Modified: 2026-11-10T21:46:32.527
Link: CVE-2026-58805
Redhat
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.