A physical occupant on an Android Automotive OS (AAOS) Multi-User Multi-Display (MUMD) passenger display can view
Source GCVE Database
Not known to be exploited.
Data as of 2 Nov 2026, 22:16 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 vulnerability in Android Automotive OS (AAOS) Multi-User Multi-Display (MUMD) passenger displays allows a physical occupant to view sensitive Heads-Up Notification (HUN) content and perform actions for a secure passenger user without authentication. This occurs because the HUN system only checks the global keyguard state linked to the driver's unlocked display, and the PassengerKeyguard fails to suppress notifications or intercept action intents. As a result, private notification data can be exposed and unauthorized actions executed without credential verification.