Quick answers
- Is CVE-2026-49906 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49906 being exploited in the wild.
- How severe is CVE-2026-49906?
- 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-49906?
- Yes: fixed in Android 14, 15, 16, 16-qpr2, 17 with security patch level 2026-11-01 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49906 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-49906?
- 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 security patch level 2026-11-01 or later
Technical details
The vulnerability is an elevation of privilege (EOP) flaw in ClusterHomeSample where an unprivileged app registers an activity with the `android.car.cluster.NAVIGATION` category and requests navigation focus. The privileged ClusterHomeSample component, acting as a confused deputy, resolves and launches this third-party activity on the instrument cluster display without enforcing the required `android.car.permission.CAR_DISPLAY_IN_CLUSTER` permission check. Network access is not required; a local attacker with the ability to install applications can exploit this.
Affected products
- Google Android Automotive OS 14, 15, 16, 16-qpr2, 17