Skip to content
Mobile

CVE-2026-5804

8.4
High
EPSS 0.26%May 20, 2026

Auth bypass in Motorola Factory Test app exposes device settings via TCP server

common questions

Is CVE-2026-5804 being exploited?

Not confirmed. CVE-2026-5804 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.

How severe is CVE-2026-5804?

CVE-2026-5804 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-5804?

Not known from our data. No patch reference has been recorded for CVE-2026-5804, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-5804 affect?

CVE-2026-5804 affects Motorola Android devices, com.motorola.motocit Factory Test app. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-5804?

Monitor advisories and patch when available; disable unused Factory Test app if feasible.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Motorola Android devicescom.motorola.motocit Factory Test app
impact

Local attacker bypasses authentication via a writable external storage descriptor to open a TCP server and access protected device settings.

action required

Monitor only

affected versions
Motorola Phones
  • affected< 2026-04-05

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free