Skip to content
IoT

CVE-2026-8982

10.0
Critical
EPSS 0.38%Jul 22, 2026

Undocumented admin backdoors in Autel Maxi Charger firmware enable full admin access.

common questions

Is CVE-2026-8982 being exploited?

Not confirmed. CVE-2026-8982 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-8982?

CVE-2026-8982 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-8982?

Not known from our data. No patch reference has been recorded for CVE-2026-8982, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-8982 affect?

CVE-2026-8982 affects Autel Maxi Charger Single firmware (<= V1.03.51), Web management interface. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-8982?

Isolate affected devices, restrict web UI access, rotate credentials, apply vendor patch ASAP.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Autel Maxi Charger Single firmware (<= V1.03.51)Web management interface
impact

Authentication bypass via vendor-derived backdoor passwords allowing admin web UI access, device takeover, config changes, data access, and lateral movement.

action required

Immediate action required

affected versions
Autel MaxiCharger Single
  • affected<= V1.03.51

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free