Quick answers
- Is CVE-2026-58927 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58927 being exploited in the wild.
- How severe is CVE-2026-58927?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Google Android 14, 15, 16, 16-qpr2, 17; Google Android Automotive OS 14, 15, 16, 16-qpr2, 17.
- Is there a fix for CVE-2026-58927?
- Yes: fixed in Android 14, 15, 16, 16-qpr2, 17 (2026-11-01 security patch level). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58927 attacked?
- It is attacked from the adjacent network, in an operating system.
- Am I affected by CVE-2026-58927?
- Check whether you run Google Android or 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 14, 15, 16, 16-qpr2, 17 (2026-11-01 security patch level)
Technical details
A use-after-free vulnerability exists in EvsEnumerator::openCamera() due to an unsynchronized std::weak_ptr that creates a data race condition. Concurrent calls from a privileged UID can cause a torn weak_ptr state, leading to a virtual function call through a freed object's vtable, enabling code execution in the hal_evs_default process.
Affected products
- Google Android 14, 15, 16, 16-qpr2, 17
- Google Android Automotive OS 14, 15, 16, 16-qpr2, 17
Timeline
- 2026-11-02: disclosed
- 2026-11-02: advisory: Android Automotive OS security bulletin published