# CVE-2026-58915: Android Automotive OS Heads-Up Notification disclosure in MUMD

Source: https://junglewise.ai/threats/cve-2026-58915-a-physical-occupant-on-an-android-automotive-os-aaos-multi-user  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-02. Updated: 2026-11-02  
License: CC BY 4.0 with a link back

CVE-2026-58915 · Severity: info · Published 2026-11-02

Android Automotive OS multi-user multi-display systems allow a physical occupant to view sensitive notifications and trigger actions for a secure passenger user without authentication. This bypasses the passenger keyguard protection and can expose private notification data and enable unauthorized user actions, creating a privacy and security risk for multi-occupant vehicles.

Technologies: [Google Android Automotive OS](https://junglewise.ai/threats/technologies/android-automotive-os). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## 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

## References

- [https://source.android.com/docs/security/bulletin/aaos/2026/2026-11-01](https://source.android.com/docs/security/bulletin/aaos/2026/2026-11-01)

## Related threats

- [Android SystemUI signature validation bypass in RemoteQCController](https://junglewise.ai/threats/cve-2026-58930-an-unprivileged-application-can-exploit-a-lack-of-package)
- [Android EVS AIDL HAL use-after-free in openCamera](https://junglewise.ai/threats/cve-2026-58927-the-vulnerability-is-a-use-after-free-uaf-in-the-evs-aidl-hal)
- [Android Automotive OS heap out-of-bounds read in EVS HAL](https://junglewise.ai/threats/cve-2026-58924-the-vulnerability-is-a-heap-out-of-bounds-read-in-the-evs-hal-s)
- [Android Automotive OS permission bypass in ClusterHomeSample](https://junglewise.ai/threats/cve-2026-49906-an-unprivileged-application-can-bypass-the-android-car-permission)
- [Android System permission bypass in DeviceAdminAppsPreferenceController](https://junglewise.ai/threats/cve-2026-28647-in-updatestate-of-deviceadminappspreferencecontroller-java-there)