An unprivileged application can exploit a lack of package/signature validation in SystemUI's `RemoteQCController` when resolving a…
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 14, 15, 16, 17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 14, 15, 16, 17.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 14, 15, 16, 17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The vulnerability affects Android's SystemUI component, specifically its Quick Controls panel handling (RemoteQCController). An unprivileged app could impersonate a legitimate content provider, inject spoofed controls into the trusted panel, and gain the ability to launch activities in the background when a user taps them.
Read the original description
An unprivileged application can exploit a lack of package/signature validation in SystemUI's `RemoteQCController` when resolving a hardcoded `content://` URI. This allows the attacker to squat on a specific authority if the legitimate package is absent, inject spoofed UI elements into the trusted SystemUI Quick Controls panel, and gain a Background Activity Launch (BAL) grant from SystemUI when the user interacts with the spoofed element.
What to do
Upgrade to a fixed version: 14, 15, 16, 17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
17, 16, 15, 14
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58930
What does this mean?
The advisory classifies CVE-2026-58930 as an elevation of privilege issue rated High. It involves SystemUI's RemoteQCController, which lacks package and signature validation, so an unprivileged application can gain higher privileges.Source: source.android.com
Am I affected, and how do I check?
Google's advisory lists Android 14, 15, 16 and 17 under the fix versions, but the facts give no affected version ranges or setup conditions. To check a device, open Settings, go to About phone, and read the Android version and security patch level.Source: source.android.com
What should I do about it?
Install the Google Android security update for your version that the advisory lists as the fix for Android 14, 15, 16 or 17.Source: source.android.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data