Skip to main content
VulnerabilityPublished

CVE-2026-58805: In multiple locations, there is a possible way to zero arbitrary secure memory via unvalidated image

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-58805

Not known to be exploited.

Data as of 10 Nov 2026, 23:19 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GoogleAndroidAffected
  • =Android kernel
Fixed in–

Description

This vulnerability (CVE-2026-58805) involves a missing bounds check in multiple locations that allows zeroing of arbitrary secure memory via unvalidated image body addresses. Exploitation requires system execution privileges but no user interaction. This could lead to physical escalation of privilege.

References

Community reviews

Loading reviews…