Quick answers
- Is CVE-2026-58930 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58930 being exploited in the wild.
- How severe is CVE-2026-58930?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Google Android 14, 15, 16, 17; Google Android Automotive OS 14, 15, 16, 17.
- Is there a fix for CVE-2026-58930?
- Yes: fixed in Android 14, 15, 16, 17 with security patch dated 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-58930 attacked?
- It is attacked over the network or with local access, in an operating system.
- Am I affected by CVE-2026-58930?
- Check whether you run Google Android or 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, 17 with security patch dated 2026-11-01 or later
Technical details
The vulnerability is an elevation of privilege (EOP) in SystemUI's RemoteQCController that lacks package and signature validation when resolving a hardcoded content:// URI. An unprivileged attacker can squat on the authority when the legitimate package is absent, inject spoofed UI elements, and obtain a Background Activity Launch grant when the user interacts with the fake element. The attack requires no special privileges or user interaction beyond normal interaction with the spoofed Quick Controls.
Affected products
- Google Android 14, 15, 16, 17
- Google Android Automotive OS 14, 15, 16, 17
Timeline
- 2026-11-02: disclosed
- 2026-11-01: patched