# CVE-2026-93832: Missing authorization in Setup App

> An exported Motorola system app component allows attackers to revoke runtime permissions from other applications, bypassing security controls.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-ffwp-v8wj-w7w8

## What is CVE-2026-93832?

CVE-2026-93832 is a medium-severity missing authorization vulnerability in Motorola Setup App, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-93832?


## How do I fix CVE-2026-93832?

No fix has been published for CVE-2026-93832 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93832 being exploited?

There is no known exploitation of CVE-2026-93832 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93832 and fix it if it is affected.

What it is: CVE-2026-93832 is a medium-severity missing authorization vulnerability in Motorola Setup App, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93832 in the wild and no public exploit code.

Affected product: Motorola Setup App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93832/ (Markdown: https://insights.sbomify.com/CVE-2026-93832/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93832
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93832
- OSV: https://osv.dev/vulnerability/CVE-2026-93832

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93832/
Summaries are generated and may contain mistakes; the official description above is the record.