Unauthorized exported component in Motorola Setup App can revoke runtime permissions

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-93832?

CVE-2026-93832 is a vulnerability classified as Missing Authorization, affecting Setup App (affected versions: < 2026-01-01). This vulnerability is rated Medium, with a CVSS score of 4.8. Current sources do not report this vulnerability as exploited.

Overview

Original source data

A component of one of the Motorola system applications was exported without permission, allowing for the revocation of runtime permissions from other apps.

Affected products and scope

  • Motorola Setup App, identified by the advisory as the MBG Setup Application or MBG Setup APK: the affected data records version: 0 with lessThan: 2026-01-01 and versionType: SPL; the default status is unaffected.
  • The vendor solution requires upgrading the Setup application to a version later than the 2026-01-01 SPL.
  • The record does not enumerate device models or separate parallel release branches, so coverage outside this SPL boundary is not further classified.

Technical details

Motorola Setup App contains a component that was exported without the authorization check needed to restrict callers. This is a missing authorization weakness, classified as CWE-862. A local application with low privileges can reach the exported component without user interaction, and the documented effect is revocation of runtime permissions from other applications. Public material does not disclose the component name, IPC entry point, attacker-controlled parameters, required Android permission, or exact device models, so the precise trigger and affected configurations remain unknown.

Exploitability

The vulnerability is reachable locally on the device, not remotely over a network. The supplied attack characteristics require low privileges, have low complexity, and do not require user interaction. The record does not identify a public exploit, and the known-exploited field is not populated; those facts do not establish that exploitation has never occurred. No usable exploit steps or proof of concept are documented.

Technical impact

Successful abuse can modify the runtime permission state belonging to other applications without authorization. The direct consequence is loss of permissions by target applications, which may prevent protected operations or cause user-visible errors. The supplied assessment indicates an integrity effect without a confidentiality effect; the record does not establish data theft or remote compromise. Availability or service impact is a possible secondary consequence rather than a universally documented outcome.

Business impact

Unauthorized permission revocation can change the security state of other applications and may prevent them from accessing protected functions or data they previously used. This can cause application malfunction or service disruption on the device, but the record does not establish a broader compromise scenario. The supplied assessment identifies an integrity impact and no direct confidentiality impact. The attacker must already have local, low-privilege execution; this is not described as a remote network issue.

Remediation

  1. Upgrade the Setup application on the device to a version later than the 2026-01-01 SPL, following Motorola's guidance.
  2. Prioritize devices whose Setup App or MBG Setup APK is running an SPL earlier than that boundary, and confirm after the upgrade that the installed version has changed.
  3. Use MDM or device-management inventory to track devices for which the Setup App SPL cannot yet be verified.
  4. The public advisory does not document a workaround, component disablement method, or alternative mitigation. Do not infer one beyond the vendor-confirmed upgrade.

Detection

  1. Inventory Motorola devices running Android and identify the Setup App, specifically the MBG Setup Application or MBG Setup APK.
  2. Use MDM, device-management tooling, or the device software-management interface to check the Setup App SPL.
  3. Compare the result with the 2026-01-01 boundary in the record: devices with an earlier SPL require handling under Motorola's upgrade guidance.
  4. Review available audit logs for unexpected changes to another application's runtime permissions as a precaution. Motorola does not provide a specific IOC or log signature, and the absence of log evidence does not prove that a device is safe.
  5. After upgrading, verify the installed Setup App version and actual SPL. The record does not provide a component name or dedicated telemetry for direct verification.
Sources (12)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.