VulnerabilityPublished 2 Nov 2026

CVE-2026-58871: In set_type4_frame_classifier of sta_iface.cpp, there is a possible memory safety issue due to a heap

Source GCVE Database

Compare

Authoritative record:CVE-2026-58871· High

Not known to be exploited.

Data as of 2 Nov 2026, 23:13 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-6cj3-g554-q68h

What to do

Affected software

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

AI-suggested

Until a fix is released, restrict local access to trusted users only and monitor for updates from the vendor.

Description

A heap buffer overflow vulnerability exists in the set_type4_frame_classifier function of sta_iface.cpp. This memory safety issue could allow local escalation of privilege without requiring additional execution privileges or user interaction.

Impact

Successful exploitation of this heap buffer overflow vulnerability can result in local privilege escalation, allowing an attacker to increase their access rights on the affected system. No additional execution privileges or user interaction are needed for exploitation, which increases the risk if an attacker has local access. There is no indication of remote exploitation or active exploitation in the wild.

References

Community reviews

Loading reviews…