Read the docs
TI-2026-84104 Aliases CVE-2026-58915GHSA-jgqv-5673-896c

Keyguard bypass exposes notifications in Android Automotive OS

Priority LOW 28CWE-287Published · Updated

Key facts

Attack vector
Physical
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-287.

Summary

Google Android versions from 14, 15, 16, 16-qpr2 and 17 are affected in Android Automotive OS Multi-User Multi-Display configurations. The Heads-Up Notification system checks only the global keyguard state, which is tied to the driver's display, and the PassengerKeyguard fails to suppress notifications or intercept action PendingIntents, an improper authentication flaw (CWE-287). A physical occupant of a passenger display can view private notification content and execute actions for a secure passenger user without authenticating.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

A physical occupant on an Android Automotive OS (AAOS) Multi-User Multi-Display (MUMD) passenger display can view sensitive Heads-Up Notification (HUN) content and execute actions for a secure passenger user (User N) without authenticating. This bypasses the PassengerKeyguard because the HUN system only checks the global keyguard state, which is tied to the driver's unlocked display, and the PassengerKeyguard implementation fails to suppress HUNs or intercept action PendingIntents. Consequently, private notification data is disclosed, and user-N actions are executed without credential verification.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00124 2nd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GoogleAndroid17; 16-qpr2; 16; 15; 14—No fix listedCNA
  • Android VendorGoogle Affected 17; 16-qpr2; 16; 15; 14 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:o:google:android:*:*:*:*:*:*:*:*——Google
  • cpe:2.3:o:google:android:*:*:*:*:*:*:*:* Versions — — ·Google

Remediation

The sources list no fixed version for Android.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Timeline

  1. 2026-11-02 Threatist record created from CVE-2026-58915
  2. 2026-11-02 Alias added: GHSA-jgqv-5673-896c
  3. 2026-11-03 CVSS score added · CISA ADP
  4. 2026-11-03 Weakness changed · CISA ADP
  5. 2026-11-03 CISA SSVC decision points changed

References

Other 1

  • TI-2025-09686 Type confusion in Google Chrome KEVCVSS 3.1CRITICAL 9.8
  • TI-2024-07390 Type confusion in Google Chrome KEVCVSS 3.1CRITICAL 9.6
  • TI-2024-04898 Type confusion in Google Chrome KEVCVSS 3.1CRITICAL 9.6
  • TI-2024-04600 Type confusion in Google Chrome KEVCVSS 3.1CRITICAL 9.6
  • TI-2024-04346 Use after free in Google Chrome KEVCVSS 3.1CRITICAL 9.6
  • TI-2023-05824 Integer overflow in Google Chrome KEVCVSS 3.1CRITICAL 9.6
See all 17247 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences