CVE-2026-0073

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-04. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
42.1%
KEV
Not listed

Published

May 4, 2026

Last Modified

May 5, 2026

Advisory Details (1)

Auto-updated May 4, 2026
No patch confirmed yet.
generic

Android Security Bulletin—May 2026  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/2026/2026-05-01

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 123 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:02 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-13 22:30 UTCEPSS rescore
  11. 2026-07-13 06:12 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-08 15:15 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-01 15:06 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 75 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-23 21:32 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-17 17:53 UTCEPSS rescore
  18. 2026-06-16 17:52 UTCEPSS rescore
  19. 2026-06-15 17:48 UTCEPSS rescore
  20. 2026-06-15 06:35 UTCGHSA enrichment
  21. 2026-06-14 23:18 UTCEPSS rescore
  22. 2026-06-14 19:20 UTCGHSA enrichment
  23. 2026-06-14 08:09 UTCGHSA enrichment
  24. 2026-06-13 23:00 UTCEPSS rescore
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 07:30 UTCGHSA enrichment
  28. 2026-06-11 20:14 UTCGHSA enrichment
  29. 2026-06-11 14:00 UTCEPSS rescore
  30. 2026-06-11 09:02 UTCGHSA enrichment
  31. 2026-06-10 22:18 UTCEPSS rescore
  32. 2026-06-10 21:49 UTCGHSA enrichment
  33. 2026-06-10 13:22 UTCEPSS rescore
  34. 2026-06-10 10:38 UTCGHSA enrichment
  35. 2026-06-09 23:13 UTCGHSA enrichment
  36. 2026-06-09 09:50 UTCGHSA enrichment
  37. 2026-06-08 22:39 UTCGHSA enrichment
  38. 2026-06-08 14:17 UTCEPSS rescore
  39. 2026-06-08 14:17 UTCEPSS rescore
  40. 2026-06-08 10:25 UTCGHSA enrichment
  41. 2026-06-07 23:14 UTCGHSA enrichment
  42. 2026-06-07 12:03 UTCGHSA enrichment
  43. 2026-06-07 00:52 UTCGHSA enrichment
  44. 2026-06-06 13:47 UTCEPSS rescore
  45. 2026-06-06 13:47 UTCEPSS rescore
  46. 2026-06-06 13:47 UTCEPSS rescore
  47. 2026-06-06 13:40 UTCGHSA enrichment
  48. 2026-06-06 02:23 UTCGHSA enrichment
  49. 2026-06-05 22:47 UTCEPSS rescore
  50. 2026-06-05 14:58 UTCGHSA enrichment
  51. 2026-06-05 06:10 UTCEPSS rescore
  52. 2026-06-05 06:10 UTCEPSS rescore
  53. 2026-06-05 03:45 UTCGHSA enrichment
  54. 2026-06-04 16:34 UTCGHSA enrichment
  55. 2026-06-04 13:12 UTCEPSS rescore
  56. 2026-06-04 13:12 UTCEPSS rescore
  57. 2026-06-04 13:12 UTCEPSS rescore
  58. 2026-06-04 05:23 UTCGHSA enrichment
  59. 2026-06-03 18:06 UTCGHSA enrichment
  60. 2026-06-03 06:55 UTCGHSA enrichment
  61. 2026-06-02 20:13 UTCEPSS rescore
  62. 2026-06-02 20:13 UTCEPSS rescore
  63. 2026-06-02 19:39 UTCGHSA enrichment
  64. 2026-06-02 08:23 UTCGHSA enrichment
  65. 2026-06-01 21:11 UTCGHSA enrichment
  66. 2026-06-01 13:51 UTCEPSS rescore
  67. 2026-06-01 13:51 UTCEPSS rescore
  68. 2026-06-01 13:51 UTCEPSS rescore
  69. 2026-06-01 10:00 UTCGHSA enrichment
  70. 2026-05-31 22:30 UTCEPSS rescore
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-29 13:44 UTCEPSS rescore
  73. 2026-05-29 13:44 UTCEPSS rescore
  74. 2026-05-28 13:44 UTCEPSS rescore
  75. 2026-05-28 13:44 UTCEPSS rescore

Publicly available exploits

(10 references)

Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCctnBobong32/CVE-2026-0073-Android-ADBD-bypass-POC_zh_CN
    First seen Jun 27, 2026

    CVE-2026-0073-Android-ADBD-bypass-POC汉化版

    Open source ↗
  • GitHub PoC0xbinder/CVE-2026-0073
    First seen May 20, 2026

    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.

    Open source ↗
  • GitHub PoCtc4dy/CVE-2026-0073-PoC-Exploit
    First seen May 13, 2026

    🚀 CVE-2026-0073 - Android ADB Wireless Debugging Exploit (CVSS 8.8) 🔓 Zero-click authentication bypass via TLS type confusion. Gain interactive shell, execute commands, scan networks. Educational red-team tool. 🐚⚡

    Open source ↗
  • GitHub PoCunnaim/adbHijacker
    First seen May 7, 2026

    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

    Open source ↗
  • GitHub PoC0xBlackash/CVE-2026-0073
    First seen May 7, 2026

    CVE-2026-0073

    Open source ↗
  • GitHub PoCdevtint/CVE-2026-0073
    First seen May 6, 2026

    https://devtint.github.io/CVE-2026-0073/

    Open source ↗
  • GitHub PoCadityatelange/poc-CVE-2026-0073
    First seen May 6, 2026

    CVE-2026-0073 - ADB Wireless Mutual Authentication Bypass PoC

    Open source ↗
  • GitHub PoCMartinPSDev/CVE-2026-0073-Android-ADBD-bypass-POC
    First seen May 6, 2026

    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+.

    Open source ↗
  • GitHub PoCSecTestAnnaQuinn/CVE-2026-0073-Android-adbd-authentication-bypass-POC
    First seen May 5, 2026
    Open source ↗
  • GitHub PoCnovaek/CVE-2026-0073-Research
    First seen May 5, 2026

    CVE-2026-0073 is an RCE with a CVSS severity score of 8.3, and here we will explain how it works.

    Open source ↗

Frequently asked(5)

What is CVE-2026-0073?
CVE-2026-0073 is a high vulnerability published on May 4, 2026. In adbdtlsverify_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…
When was CVE-2026-0073 disclosed?
CVE-2026-0073 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on May 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0073 actively exploited?
CVE-2026-0073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-0073?
CVE-2026-0073 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-0073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0073, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0073

Explore →

Is Your Infrastructure Affected by CVE-2026-0073?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs