VulnerabilityPublished 2 Nov 2026

CVE-2026-58876: In multiple locations, there is a possible memory safety issue due to a use-after-free

Source GCVE Database

Compare

Authoritative record:CVE-2026-58876· High

Not known to be exploited.

Data as of 2 Nov 2026, 23:00 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

Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-9xx6-8634-p8rf

What to do

Affected software

Product	Affected	Fixed in
GoogleAndroid	Affected 14 – 17 5 affected builds	Fixed in–

Description

A use-after-free memory safety issue exists in multiple locations, potentially allowing remote code execution without requiring additional privileges or user interaction.

Impact

Successful exploitation may result in remote code execution, which could allow an attacker to execute arbitrary code on the affected system without requiring additional privileges or user interaction.

Summary

This vulnerability involves a use-after-free condition in multiple locations within the affected software. Exploitation could lead to remote code execution without needing extra execution privileges or user interaction.

References

Community reviews

Loading reviews…