# CVE-2026-28625: Android Automotive OS permission bypass in System component

Source: https://junglewise.ai/threats/cve-2026-28625-in-multiple-locations-there-is-a-possible-permission-bypass-due  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-05. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-28625 · Severity: info · Published 2026-10-05

Android Automotive OS (AAOS), which runs on vehicle infotainment and control systems, contains a logic error that allows unauthorized users to bypass permission checks. An attacker can exploit this locally to gain elevated privileges on an affected vehicle's system without requiring special access or user interaction, potentially compromising vehicle functions and data.

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-28625 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-28625 being exploited in the wild.

**How severe is CVE-2026-28625?** Informational severity, published 5 October 2026.

**Which products and versions are affected?** Google Android Automotive OS versions prior to Android 14, 15, 16, 16-qpr2, and 17.

**Is there a fix for CVE-2026-28625?** Yes: fixed in Android 14, 15, 16, 16-qpr2, 17. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-28625 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-28625?** 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

## Technical details

A logic error in the System component of Android Automotive OS enables local privilege escalation through permission bypass. No additional execution privileges are required for exploitation, and user interaction is not needed. The vulnerability affects multiple code locations and is fixed in AOSP versions 14, 15, 16, 16-qpr2, and 17.

## Affected products

- Google Android Automotive OS versions prior to Android 14, 15, 16, 16-qpr2, and 17

## Timeline

- 2026-10-05: disclosed: Android Security Bulletin published

## References

- [https://source.android.com/docs/security/bulletin/aaos/2026/2026-10-01](https://source.android.com/docs/security/bulletin/aaos/2026/2026-10-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 Heads-Up Notification disclosure in MUMD](https://junglewise.ai/threats/cve-2026-58915-a-physical-occupant-on-an-android-automotive-os-aaos-multi-user)
- [Android Automotive OS permission bypass in ClusterHomeSample](https://junglewise.ai/threats/cve-2026-49906-an-unprivileged-application-can-bypass-the-android-car-permission)