CVE-2026-0073
Wireless ADB mutual-auth bypass enables remote code execution.
Is CVE-2026-0073 being exploited?
Not confirmed. CVE-2026-0073 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.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-0073?
CVE-2026-0073 is rated High with a CVSS score of 8.8. 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-0073?
Yes. A fix has been recorded for CVE-2026-0073. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-0073 affect?
CVE-2026-0073 affects Android devices with wireless ADB enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0073?
Disable wireless ADB; restrict adbd access; patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote RCE as shell user via proximity wireless ADB; no user interaction required.
Immediate action required
- affected16-qpr2
- affected16
- affected15
- affected14
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.