Quick answers
- Is CVE-2026-8989 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8989 being exploited in the wild.
- How severe is CVE-2026-8989?
- Informational severity, with a CVSS score of 8.6, published 21 July 2026.
- Which products and versions are affected?
- Autel MaxiCharger Single through V1.03.51.
- Is there a fix for CVE-2026-8989?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-8989 attacked?
- It is attacked with physical access, in a network appliance.
- Am I affected by CVE-2026-8989?
- Check whether you run Autel MaxiCharger Single at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Autel MaxiCharger Single utilizes an NXP i.MX6 processor which, in affected firmware versions up to V1.03.51, permits unrestricted access to the chip's Serial Download Mode (recovery mode). An attacker with physical access to the device's internal PCB can force the processor into this mode by short-circuiting two specific hardware recovery pins. Once in recovery mode, the attacker can boot arbitrary, attacker-controlled code directly into RAM. This bypasses standard boot protections, allowing for the modification or extraction of the device's filesystem, firmware, and other sensitive internal data.
Affected products
- Autel MaxiCharger Single through V1.03.51
Timeline
- 2026-07-21: advisory: NVD publication date
- 2026-09-06: disclosed: CyberDanube research publication date