CVE-2026-58930: URI squatting enables spoofed

CISO Take

CVE-2026-58930 is a flaw in Android Automotive OS SystemUI. The RemoteQCController resolves a hardcoded content:// URI without checking the package or signature of the provider. An unprivileged app can claim that authority when the legitimate package is absent, inject spoofed elements into the trusted Quick Controls panel, and receive a Background Activity Launch grant when the user taps one. Nothing in the record ties this to an AI/ML product or package: the 'ml_ui' category looks like a misclassification, and the AI exposure is indirect at most (in-vehicle assistants or ML apps running on the same platform). There is no CVSS, EPSS or SSVC data, no public exploit or scanner template, and it is not in CISA KEV, so urgency is low and the data is incomplete. Fleet owners, OEMs and automotive teams should apply the 2026-11-01 Android Automotive OS security bulletin patch level and check whether unapproved apps can be installed on their head units.

Sources:NVDsource.android.com

What is the risk?

Severity is unrated (no CVSS, EPSS or SSVC). The flaw is a local privilege and trust-boundary issue: an installed unprivileged app can impersonate a trusted system UI surface and obtain a BAL grant, which needs user interaction. There is no evidence of exploitation, no public exploit and no KEV listing. Risk is limited to devices running affected Android Automotive OS builds where the legitimate provider package is missing and a malicious app can be installed. Direct risk to AI/ML systems is low. This is not an ML framework vulnerability, and the 'ml_ui' tag is probably an artifact of the classifier.

How does the attack unfold?

Initial Access

A malicious unprivileged app is installed on a device where the legitimate Quick Controls provider package is absent.

Authority Squatting

The app registers a ContentProvider on the hardcoded content:// authority that SystemUI's RemoteQCController resolves without package or signature validation.

UI Spoofing

SystemUI loads the attacker's controls into the trusted Quick Controls panel, and the user taps a spoofed element.

Impact

SystemUI's Background Activity Launch grant lets the attacker's activity start in the foreground, enabling phishing or UI deception.

Initial Access

A malicious unprivileged app is installed on a device where the legitimate Quick Controls provider package is absent.

Authority Squatting

The app registers a ContentProvider on the hardcoded content:// authority that SystemUI's RemoteQCController resolves without package or signature validation.

UI Spoofing

SystemUI loads the attacker's controls into the trusted Quick Controls panel, and the user taps a spoofed element.

Impact

SystemUI's Background Activity Launch grant lets the attacker's activity start in the foreground, enabling phishing or UI deception.

How severe is it?

CVSS 3.1

N/A

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

Moderate

What should I do?

1 step

1) Apply the Android Automotive OS patch level from the 2026-11-01 bulletin (source.android.com/docs/security/bulletin/aaos/2026/2026-11-01) through the OEM or vendor update channel. 2) Ensure the legitimate package that owns the Quick Controls authority is installed on all builds, since the squatting only works when it is absent. 3) Restrict sideloading and app installation on automotive head units, and enforce app allowlists through MDM or the fleet management platform. 4) Detect by auditing installed apps that declare ContentProviders with authorities matching those SystemUI resolves, and by monitoring unexpected background activity launches from SystemUI. 5) Confirm with the OEM or Android vendor which exact builds are affected, because the record lists no affected products.

How is it classified?

Auth BypassSocial EngineeringFramework

Which compliance frameworks are affected?

This CVE is relevant to:

NIST AI RMF

MANAGE 2.3-Mechanisms to respond to and recover from previously unknown risks

Frequently Asked Questions

What is CVE-2026-58930?

CVE-2026-58930 is a flaw in Android Automotive OS SystemUI. The RemoteQCController resolves a hardcoded content:// URI without checking the package or signature of the provider. An unprivileged app can claim that authority when the legitimate package is absent, inject spoofed elements into the trusted Quick Controls panel, and receive a Background Activity Launch grant when the user taps one. Nothing in the record ties this to an AI/ML product or package: the 'ml_ui' category looks like a misclassification, and the AI exposure is indirect at most (in-vehicle assistants or ML apps running on the same platform). There is no CVSS, EPSS or SSVC data, no public exploit or scanner template, and it is not in CISA KEV, so urgency is low and the data is incomplete. Fleet owners, OEMs and automotive teams should apply the 2026-11-01 Android Automotive OS security bulletin patch level and check whether unapproved apps can be installed on their head units.

Is CVE-2026-58930 actively exploited?

No confirmed active exploitation of CVE-2026-58930 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-58930?

1) Apply the Android Automotive OS patch level from the 2026-11-01 bulletin (source.android.com/docs/security/bulletin/aaos/2026/2026-11-01) through the OEM or vendor update channel. 2) Ensure the legitimate package that owns the Quick Controls authority is installed on all builds, since the squatting only works when it is absent. 3) Restrict sideloading and app installation on automotive head units, and enforce app allowlists through MDM or the fleet management platform. 4) Detect by auditing installed apps that declare ContentProviders with authorities matching those SystemUI resolves, and by monitoring unexpected background activity launches from SystemUI. 5) Confirm with the OEM or Android vendor which exact builds are affected, because the record lists no affected products.

What systems are affected by CVE-2026-58930?

This vulnerability affects the following AI/ML architecture patterns: Android Automotive OS head units, In-vehicle UI and Quick Controls surfaces, On-device AI assistants sharing the Android platform (indirect).

What is the CVSS score for CVE-2026-58930?

No CVSS score has been assigned yet.

What is the AI security impact?

Affected AI Architectures

Android Automotive OS head unitsIn-vehicle UI and Quick Controls surfacesOn-device AI assistants sharing the Android platform (indirect)

Compliance Controls Affected

NIST AI RMF: MANAGE 2.3

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An attacker publishes an app that looks harmless and gets it installed on a vehicle head unit that lacks the legitimate Quick Controls provider package. The app registers a ContentProvider on the hardcoded authority SystemUI queries. SystemUI loads the attacker's entries into the Quick Controls panel without validating the package or signature. The driver or passenger taps a spoofed control that looks like a trusted system toggle, and SystemUI's BAL grant lets the attacker's activity launch in the foreground, for example a credential-harvesting screen. If an AI voice assistant or ML-based app is the target, the spoofed UI could imitate it, but that is a secondary effect.