Google Android 14/15/16/16-qpr2 auth.cpp adbd_tls_verify_cert incorrect implementation of authentication algorithm
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $25k-$100k | 0.00 |
Summary
A vulnerability was found in Google Android 14/15/16/16-qpr2. It has been classified as critical. Affected by this vulnerability is the function adbd_tls_verify_cert of the file auth.cpp. This manipulation causes incorrect implementation of authentication algorithm.
The identification of this vulnerability is CVE-2026-0073. The attack needs to be done within the local network. There is no exploit available.
Details
A vulnerability classified as critical was found in Google Android 14/15/16/16-qpr2. Affected by this vulnerability is the function adbd_tls_verify_cert of the file auth.cpp. The manipulation with an unknown input leads to a incorrect implementation of authentication algorithm vulnerability. The CWE definition for the vulnerability is CWE-303. The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at source.android.com. This vulnerability is known as CVE-2026-0073 since 10/15/2025. The exploitation appears to be easy. Access to the local network is required for this attack. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 05/04/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.8
VulDB Base Score: 8.8
VulDB Temp Score: 8.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 8.8
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Incorrect implementation of authentication algorithmCWE: CWE-303
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/15/2025 CVE reserved05/04/2026 Advisory disclosed
05/04/2026 VulDB entry created
05/04/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CVE: CVE-2026-0073 (🔒)
GCVE (CVE): GCVE-0-2026-0073
GCVE (VulDB): GCVE-100-361009
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 05/04/2026 22:49Changes: 05/04/2026 22:49 (65)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.