# CVE-2026-8989: Open Recovery Mode

> Physical attackers can bypass security restrictions via exposed recovery pins to execute arbitrary code and extract sensitive data from Autel Maxi Charger devices.

- **Severity:** High 8.6 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-wpf3-8j9v-2qg2

## What is CVE-2026-8989?

CVE-2026-8989 is a high-severity vulnerability in Autel MaxiCharger Single, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-1244 (Internal Asset Exposed to Unsafe Debug Access Level or State), CWE-1191 (On-Chip Debug and Test Interface With Improper Access Control)

## Which versions are affected by CVE-2026-8989?

It affects 1 product.


Products: Autel Maxicharger Single Charger Firmware.

## How do I fix CVE-2026-8989?

No fix has been published for CVE-2026-8989 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8989 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8989 exists.

## Other vulnerabilities in Autel MaxiCharger Single

- [CVE-2026-8982](https://insights.sbomify.com/CVE-2026-8982/): Hard-coded / Backdoor Accounts (critical 10.0)
- [CVE-2026-8983](https://insights.sbomify.com/CVE-2026-8983/): Backdoor Authentication Token (critical 10.0)
- [CVE-2026-8984](https://insights.sbomify.com/CVE-2026-8984/): Unauthenticated RCE (critical 10.0)
- [CVE-2026-8985](https://insights.sbomify.com/CVE-2026-8985/): Unauthenticated Command Injection (critical 10.0)
- [CVE-2026-8986](https://insights.sbomify.com/CVE-2026-8986/): Command Injection via Malicious OCPP Server (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8989 and fix it if it is affected.

What it is: CVE-2026-8989 is a high-severity vulnerability in Autel MaxiCharger Single, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8989 exists.

Affected product: Autel MaxiCharger Single. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8989/ (Markdown: https://insights.sbomify.com/CVE-2026-8989/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8989
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8989
- OSV: https://osv.dev/vulnerability/CVE-2026-8989

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8989/
Summaries are generated and may contain mistakes; the official description above is the record.