Autel MaxiCharger Single up to 1.03.51 UART interface access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $0-$5k | 1.22 |
Summary
A vulnerability was found in Autel MaxiCharger Single up to 1.03.51. It has been rated as very critical. This vulnerability affects unknown code of the component UART interface. The manipulation leads to access control. This vulnerability is referenced as CVE-2026-8988. The attack can only be performed from a local environment. No exploit is available.
Details
A vulnerability, which was classified as very critical, has been found in Autel MaxiCharger Single up to 1.03.51. This issue affects an unknown function of the component UART interface. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Autel Maxi Charger Single firmware through V1.03.51 exposes an accessible UART interface that permits interruption of the boot process and access to the U-Boot bootloader. An attacker with physical access can modify the boot configuration or file system to obtain operating system access.
It is possible to read the advisory at cyberdanube.com. The identification of this vulnerability is CVE-2026-8988 since 05/19/2026. The exploitation is known to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/22/2026). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 1.03.0
- 1.03.1
- 1.03.2
- 1.03.3
- 1.03.4
- 1.03.5
- 1.03.6
- 1.03.7
- 1.03.8
- 1.03.9
- 1.03.10
- 1.03.11
- 1.03.12
- 1.03.13
- 1.03.14
- 1.03.15
- 1.03.16
- 1.03.17
- 1.03.18
- 1.03.19
- 1.03.20
- 1.03.21
- 1.03.22
- 1.03.23
- 1.03.24
- 1.03.25
- 1.03.26
- 1.03.27
- 1.03.28
- 1.03.29
- 1.03.30
- 1.03.31
- 1.03.32
- 1.03.33
- 1.03.34
- 1.03.35
- 1.03.36
- 1.03.37
- 1.03.38
- 1.03.39
- 1.03.40
- 1.03.41
- 1.03.42
- 1.03.43
- 1.03.44
- 1.03.45
- 1.03.46
- 1.03.47
- 1.03.48
- 1.03.49
- 1.03.50
- 1.03.51
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: 🔍
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: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
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
05/19/2026 CVE reserved07/22/2026 Advisory disclosed
07/22/2026 VulDB entry created
07/22/2026 VulDB entry last update
Sources
Advisory: cyberdanube.comStatus: Not defined
CVE: CVE-2026-8988 (🔒)
GCVE (CVE): GCVE-0-2026-8988
GCVE (VulDB): GCVE-100-381395
Entry
Created: 07/22/2026 02:38Changes: 07/22/2026 02:38 (52)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.