Quick answers
- Is CVE-2026-58915 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58915 being exploited in the wild.
- How severe is CVE-2026-58915?
- 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-58915?
- Yes: fixed in Android 14, 15, 16, 16-qpr2, 17 (with 2026-11-01 security patch). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58915 attacked?
- It is attacked with physical access or from the adjacent network, in an operating system.
- Am I affected by CVE-2026-58915?
- 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 14, 15, 16, 16-qpr2, 17 (with 2026-11-01 security patch)
Technical details
The Heads-Up Notification (HUN) system in Android Automotive OS checks only the global keyguard state (driver's unlock status) rather than the per-user PassengerKeyguard, allowing physical access to intercept HUN content and pending intents. An attacker with physical access to a passenger display can view and act on notifications meant only for an authenticated user. The vulnerability affects Android 14, 15, 16, 16-qpr2, and 17.
Affected products
- Google Android Automotive OS 14, 15, 16, 16-qpr2, 17
Timeline
- 2026-11-02: disclosed
- 2026-11-02: advisory