# CVE-2026-0073: Auth bypass in Android

> A logic error in Android's wireless ADB authentication allows remote attackers to bypass mutual authentication and execute code as the shell user without user interaction.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 May 2026
- **Updated:** 5 May 2026
- **Also known as:** A-469080888, ASB-A-469080888, GHSA-6hgp-j96h-rqw4

## What is CVE-2026-0073?

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

### Official description

In adbd_tls_verify_cert of auth.cpp, there is a possible bypass of wireless ADB mutual authentication due to a logic error in the code. This could lead to remote (proximal/adjacent) code execution as the shell user with no additional execution privileges needed. User interaction is not needed for exploitation.

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm)

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

It affects 1 product.


Products: Google Android.

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

Apply the vendor's patch.

## Is CVE-2026-0073 being exploited?

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

Public exploit code:

- https://github.com/SecTestAnnaQuinn/CVE-2026-0073-Android-adbd-authentication-bypass-POC (github_poc): https://github.com/SecTestAnnaQuinn/CVE-2026-0073-Android-adbd-authentication-bypass-POC
- CVE-2026-0073 - ADB Wireless Mutual Authentication Bypass PoC (github_poc): https://github.com/adityatelange/poc-CVE-2026-0073
- An automated exploit for CVE-2026-0073 (Android ADB TLS Auth Bypass). Features a built-in mDNS/Zeroconf scanner to instantly discover randomized Wireless Debugging ports on Android 13+ and establishes a fully interactive raw PTY shell. (github_poc): https://github.com/0xbinder/CVE-2026-0073
- CVE-2026-0073 — Android ADB daemon (adbd) TLS authentication bypass via EVP_PKEY_cmp type confusion. Gain unauthorized shell access over WiFi using EC/Ed25519 key mismatch. PoC exploit for Android 14+. (github_poc): https://github.com/MartinPSDev/CVE-2026-0073-Android-ADBD-bypass-POC
- CVE-2026-0073 – Android ADB Wireless Debugging Auth Bypass (CVSS 8.8) | Zero-click TLS type confusion to unauthenticated shell. 2 tools: Full Exploit (ADB shell, cmd exec, subnet scan, mDNS, stealth, SOCKS5) & SafeDetect (non-intrusive audit, CIDR, JSON/CSV/HTML). Red/Blue team toolkit. Ethical & Safety use only. (github_poc): https://github.com/tc4dy/CVE-2026-0073-PoC-Exploit
- A PoC tool for the CVE-2026-0073 on android 11+ devices which allows instant zero click RCE on any unpatched device with adb over tcp enabled (github_poc): https://github.com/unnaim/adbHijacker

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0073 is a high-severity authentication bypass vulnerability in Google Android, published on 4 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-0073 in the wild and no public exploit code.

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

## Sources

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

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