# CVE-2026-5804: Auth bypass in Phones

> A local attacker can bypass permission checks in Motorola Factory Test to access protected device settings and sensitive data via a writable file descriptor.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 19 May 2026
- **Updated:** 19 May 2026
- **Also known as:** GHSA-5g7p-w325-jqc4

## What is CVE-2026-5804?

CVE-2026-5804 is a high-severity authentication bypass vulnerability in Motorola Phones, published on 19 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An improper authentication vulnerability was discovered in the Motorola Factory Test component (com.motorola.motocit). The application contained a reference to a writable file descriptor in external storage which could be used by third party apps running on the device to open a TCP server, exposing sensitive permissions and data. This could allow a local attacker to bypass permission checks and access protected device settings.

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


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

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

## Is CVE-2026-5804 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5804 is a high-severity authentication bypass vulnerability in Motorola Phones, published on 19 May 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-5804 in the wild and no public exploit code.

Affected product: Motorola Phones. 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-5804/ (Markdown: https://insights.sbomify.com/CVE-2026-5804/index.md)
```

## Sources

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

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