The report details a heap Use-After-Free (UAF) vulnerability within the android.hardware.automotive.evs-default HAL
Source GCVE Database
Not known to be exploited.
Data as of 2 Nov 2026, 22:17 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
Description
A heap Use-After-Free (UAF) vulnerability exists in the android.hardware.automotive.evs-default HAL service due to unsynchronized access to an std::unordered_map. An unprivileged application with EVS manager access can exploit this by concurrently calling setExtendedInfo and getExtendedInfo, potentially leading to code execution in the privileged HAL process.