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.
Severity
CVSS 3.1
8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5%(unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-303Incorrect Implementation of Authentication Algorithm
Show the promptExplain CVE-2026-0073 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-0073?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-0073?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-0073 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
0xbinder/CVE-2026-0073Harbor Check: matches CVE30 stars, Python, created An automated exploit for CVE-2026-0073 (Android ADB TLS Auth Bypass). Features a built-in mDNS/Zeroconf scanner to instantly discover rando…
MartinPSDev/CVE-2026-0073-Android-ADBD-bypass-POCHarbor Check: matches CVE25 stars, Python, created CVE-2026-0073 — Android ADB daemon (adbd) TLS authentication bypass via EVP_PKEY_cmp type confusion. Gain unauthorized shell access over Wi…
tc4dy/CVE-2026-0073-PoC-ExploitHarbor Check: matches CVE17 stars, Python, created CVE-2026-0073 – Android ADB Wireless Debugging Auth Bypass (CVSS 8.8) | Zero-click TLS type confusion to unauthenticated shell. 2 tools: Fu…
10 more
unnaim/adbHijackerHarbor Check: matches CVE9 stars, created 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 enabl…
naheeju/POC-CVE-2026-0073Harbor Check: matches CVE5 stars, Go, created Security research PoC for CVE-2026-0073: ADB authentication bypass verification
aye468448-eng/CVE-2026-0073-Android-adbd-authentication-bypassHarbor Check: matches CVE0 stars, Python, created Research on CVE-2026-0073. An auth bypass allowing any attacker with local network access to connect to an Android device with dev tools an…