CVE-2026-8983 Details
Description
Autel Maxi Charger Single firmware through V1.03.51 contains a hard-coded authentication token that bypasses authorization checks for multiple management endpoints. An attacker can supply the special token value to invoke privileged functionality without valid authentication.
A backdoor authentication token vulnerability has been identified in Autel Maxi Charger Single firmware through V1.03.51. This vulnerability allows an attacker to bypass authorization checks for multiple management endpoints by supplying a hard-coded token value. Exploitation of this vulnerability enables access to privileged functionalities and the ability to modify device configurations without valid authentication.
Users are advised to update to the latest available version and restrict network access to the devices. Additionally, physical access should be limited, as there are vulnerabilities that can be exploited with direct access to the device.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 22, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://cyberdanube.com/security-research/multiple-vulnerabilities-in-autel-maxi-charger/ | [email protected] | ExploitThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-798 | Use of Hard-coded Credentials | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| autel maxicharger single charger firmware | <= 1.03.51 |
CPE
Remediation
| |
| autel maxicharger single charger | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 12, 2026 | Initial Analysis | [email protected] |
| Jul 22, 2026 | CVE Modified | CISA-ADP |
| Jul 21, 2026 | New CVE Received | [email protected] |