CVE-2026-0073

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-27041 (ENISA EUVD) · GHSA-6hgp-j96h-rqw4 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: Public PoCExposed services: Not assessed

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

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.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 4, 2026

Last Modified

October 26, 2026

Advisory Details (1)

Auto-updated May 4, 2026
No fix on record yet.
Web page

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 12× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 260 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 160 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(12 references, 10 shown)

Public exploit code is referenced for this CVE (12 GitHub PoCs). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • GitHub PoCnaheeju/POC-CVE-2026-0073
    Published Aug 31, 2026

    Security research PoC for CVE-2026-0073: ADB authentication bypass verification

    Open source ↗
  • GitHub PoCctnBobong32/CVE-2026-0073-Android-ADBD-bypass-POC_zh_CN
    Published Jun 27, 2026

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

    Open source ↗
  • GitHub PoCctn-Qvo/CVE-2026-0073-Android-ADBD-bypass-POC_zh_CN
    Published Jun 27, 2026

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

    Open source ↗
  • GitHub PoC0xbinder/CVE-2026-0073
    Published 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
    Published 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 PoC0xBlackash/CVE-2026-0073
    Published May 7, 2026

    CVE-2026-0073

    Open source ↗
  • GitHub PoC0xredash/CVE-2026-0073
    Published May 7, 2026

    CVE-2026-0073

    Open source ↗
  • GitHub PoCunnaim/adbHijacker
    Published 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 PoCadityatelange/poc-CVE-2026-0073
    Published May 6, 2026

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

    Open source ↗
  • GitHub PoCMartinPSDev/CVE-2026-0073-Android-ADBD-bypass-POC
    Published 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 ↗

Frequently asked(5)

What is CVE-2026-0073?
CVE-2026-0073 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-0073 was made public on May 4, 2026: that is the date its CVE record's CNA, Android (associated with Google Inc. or Open Handset Alliance), gives for when the vulnerability was made public. The CVE record itself was published on May 4, 2026. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-0073 actively exploited?
CVE-2026-0073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
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?
No fix for CVE-2026-0073 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

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.