Skip to content
IoT

CVE-2026-8983

10.0
Critical
EPSS 0.43%Jul 22, 2026

Hard-coded auth token in Autel charger firmware allows admin bypass.

common questions

Is CVE-2026-8983 being exploited?

Not confirmed. CVE-2026-8983 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.43% probability of exploitation in the next 30 days.

How severe is CVE-2026-8983?

CVE-2026-8983 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-8983?

Not known from our data. No patch reference has been recorded for CVE-2026-8983, 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-8983 affect?

CVE-2026-8983 affects Autel Maxi Charger Single firmware <= V1.03.51. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-8983?

Isolate devices, disable remote management, block access, apply vendor firmware update when available.

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
impact

Auth bypass via hard-coded token grants administrative access to management endpoints: firmware/config changes, device takeover, 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