Autel MaxiCharger Single up to 1.03.51 Recovery Mode information disclosure

Summaryinfo

A vulnerability identified as problematic has been detected in Autel MaxiCharger Single up to 1.03.51. Impacted is an unknown function of the component Recovery Mode. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2026-8989. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in Autel MaxiCharger Single up to 1.03.51 and classified as problematic. Affected by this vulnerability is some unknown functionality of the component Recovery Mode. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

Autel Maxi Charger Single firmware through V1.03.51 permits unrestricted access to the NXP i.MX6 recovery mode through exposed hardware recovery pins. An attacker with physical access can boot attacker-controlled code in memory and modify or extract firmware and other sensitive data.

The advisory is shared at cyberdanube.com. This vulnerability is known as CVE-2026-8989 since 05/19/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Autel

Name

• MaxiCharger Single

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.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion