Quick answers
- Is CVE-2026-28647 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-28647 being exploited in the wild.
- How severe is CVE-2026-28647?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Google Android Automotive OS 14, 15, 16-qpr1.
- Is there a fix for CVE-2026-28647?
- Yes: fixed in Android 14, 15, 16-qpr2, 17 (2026-10-01 security patch level or later). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-28647 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-28647?
- 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-qpr2, 17 (2026-10-01 security patch level or later)
Technical details
A logic error in the updateState method of DeviceAdminAppsPreferenceController.java allows permission bypass and local privilege escalation. The vulnerability affects the System component and requires no additional execution privileges or user interaction to exploit. This is a logic-based authorization flaw in Android Automotive OS's device admin application settings.
Affected products
- Google Android Automotive OS 14, 15, 16-qpr1
Timeline
- 2026-10-05: disclosed