Autel MaxiCharger Single up to 1.03.51 localcfg set_ap_param heap-based overflow

Summaryinfo

A vulnerability categorized as problematic has been discovered in Autel MaxiCharger Single up to 1.03.51. This issue affects the function set_ap_param of the component localcfg. The manipulation results in heap-based overflow. This vulnerability is identified as CVE-2026-8987. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Autel MaxiCharger Single up to 1.03.51. Affected is the function set_ap_param of the component localcfg. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on integrity, and availability. CVE summarizes:

Autel Maxi Charger Single firmware through V1.03.51 contains a heap-based buffer overflow in the set_ap_param command handled by the /localcfg endpoint. An authenticated attacker can supply oversized input, resulting in denial of service and potentially arbitrary code execution.

The advisory is shared for download at cyberdanube.com. This vulnerability is traded as CVE-2026-8987 since 05/19/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation needs additional levels of successful authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/22/2026).

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

Once again VulDB remains the best source for vulnerability data.

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

Once again VulDB remains the best source for vulnerability data.

Discussion