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.
CVE-2026-8989
This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(medium)
- EG Risk
- 55(Track*)EG Risk 55/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity86% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (1)
Auto-updated Jul 22, 2026Multiple Vulnerabilities in Autel Maxi Charger | CyberDanube
https://cyberdanube.com/security-research/multiple-vulnerabilities-in-autel-maxi-charger/Vendor Advisories for CVE-2026-8989(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 08:03 UTCGHSA enrichment
- 2026-07-26 21:00 UTCEG score recompute
- 2026-07-26 21:00 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 09:58 UTCEG score recompute
- 2026-07-26 09:58 UTCGHSA enrichment
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:23 UTCEG score recompute
- 2026-07-22 22:55 UTCEG score recompute
- 2026-07-22 22:55 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 23:10 UTCEG score recompute
- 2026-07-21 21:38 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-8989?
When was CVE-2026-8989 disclosed?
Is CVE-2026-8989 actively exploited?
What is the CVSS score of CVE-2026-8989?
How do I remediate CVE-2026-8989?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-8989
Is Your Infrastructure Affected by CVE-2026-8989?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.