Quick answers
- Is CVE-2026-58924 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58924 being exploited in the wild.
- How severe is CVE-2026-58924?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Google Android Automotive OS 14, 15, 16, 16-qpr2, 17.
- Is there a fix for CVE-2026-58924?
- Yes: fixed in Android Automotive OS 14, 15, 16, 16-qpr2, 17 (security patch level 2026-11-01 or later). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58924 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-58924?
- Check whether you run Google Android Automotive OS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Android Automotive OS 14, 15, 16, 16-qpr2, 17 (security patch level 2026-11-01 or later)
Technical details
The vulnerability is a heap out-of-bounds read in the EVS HAL's `getStreamList()` method triggered by attacker-controlled `CameraDesc.metadata` byte arrays that are parsed without validation. An attacker can trigger an out-of-bounds read at an offset they control within the HAL process's heap, exfiltrating sensitive data like pointers and buffer handles. The issue affects Android Automotive OS versions 14, 15, 16, 16-qpr2, and 17.
Affected products
- Google Android Automotive OS 14, 15, 16, 16-qpr2, 17
Timeline
- 2026-11-02: disclosed