CVE-2026-0073 key takeaways
- Affected: 14-16
- Class: RCE (Critical)
- Resolution: May 2026 Android Security Bulletin
- Publication status: Publicly disclosed
CVE-2026-0073 technical analysis
CVE-2026-0073 is a critical-severity Android vulnerability tracked as RCE. The published record describes adbd wireless debugging remote shell affecting 14-16. In practical terms, the vulnerability should be evaluated as a specific weakness in a specific component—not as automatic evidence that every affected device can be fully compromised. The execution context, reachable interface, platform mitigations, and availability of a reliable exploit chain all shape real-world risk.
Remote code execution vulnerabilities cross a data-processing or trust boundary and cause attacker-influenced input to be interpreted as executable behavior. The practical result depends on the process that handles the input, its sandbox, entitlements, and the mitigations present on the device. For CVE-2026-0073, the confirmed impact recorded is: Full device compromise via remote shell. Attacker gains identity of shell user.
This record lists 2026-05-05 as the public disclosure or patch date, identifies 2026-04-12 as the discovery information currently available, and credits mhfh research. The remediation recorded for affected users is May 2026 Android Security Bulletin. Use the references at the end of this page as the authoritative source, because vendors can revise advisories after publication.
Attack surface and exploitation prerequisites
The delivery path matters as much as the memory-safety or logic flaw. Researchers should establish whether the vulnerable component accepts network, browser, message, media, radio, or adjacent-device input and whether any user interaction is required. An RCE in a restricted service is not automatically equivalent to full device compromise.
A defensible assessment separates reachability, exploitation, and post-exploitation, so a component-level flaw is not described as an end-to-end device takeover. Compensating controls—network segmentation, application allow-listing, restricted messaging or browsing features, and MDM-enforced patching—can reduce exposure, but the durable resolution remains the vendor update identified in this record.
Detection and forensic triage
Preserve application, browser, messaging, media-processing, and system diagnostic logs around the suspected delivery time. Look for repeated process crashes, abnormal restarts, unexpected child processes, or follow-on activity, but do not treat any single symptom as proof of exploitation.
Absence of a visible symptom does not prove absence of exploitation, and a crash alone does not prove compromise. Preserve device state, record the operating-system build and patch level, and acquire logs using a method appropriate to the legal context—resetting or repeatedly testing the device can destroy useful traces. When assessing a suspected targeted attack, correlate device evidence with account sign-ins, messaging metadata, network telemetry, and MDM events to separate attempted delivery from successful exploitation.
How to mitigate CVE-2026-0073
The primary mitigation is straightforward: Disable wireless debugging when not in use. Update to May 2026 patch level.
On Android, record both the Android version and the security patch level because the operating-system number alone does not prove that a fix is present. OEM and chipset bulletins may ship on different schedules. Google Play system updates can repair selected modular components, while firmware, kernel, and modem fixes usually depend on the device manufacturer.
- Identify the exact device model, operating-system build, and current security patch level.
- Compare that information with the affected range and fixed release documented by the vendor.
- Back up necessary evidence before making changes when compromise is suspected.
- Install the latest supported security release rather than stopping at the first version that mentions the CVE.
- Verify the installed build after reboot and review related accounts and applications for follow-on activity.
PoC interpretation and research notes
This page distinguishes public disclosure from independent reproduction. Its current status is Publicly disclosed. The record is based on the cited public disclosure and has not been represented as proprietary discovery. Any PoC shown above should be reviewed in an isolated lab and used only on systems the researcher owns or is explicitly authorized to test. Public availability is not a guarantee that code is safe, complete, or accurately attributed.
Frequently asked questions about CVE-2026-0073
What is CVE-2026-0073?
CVE-2026-0073 is a Android RCE vulnerability associated with adbd wireless debugging remote shell. It affects 14-16, according to the currently cited disclosures. The practical risk depends on the vulnerable component, required access, available mitigations, and whether the device has received May 2026 Android Security Bulletin.
Is CVE-2026-0073 being exploited in the wild?
The status on this page is “Publicly disclosed.” A vendor-confirmed vulnerability is not necessarily known to be actively exploited. This database uses “Exploited in the wild” only when a cited vendor or authoritative security source reports observed exploitation; public PoC availability is tracked separately.
How do I protect a device from CVE-2026-0073?
Install the latest supported security update and verify the resulting build or patch level. The recorded minimum resolution is May 2026 Android Security Bulletin. Apply relevant compensating controls while updates are pending, but do not treat configuration changes as equivalent to patching the underlying vulnerability.