Autel Maxi Charger Single firmware through V1.03.51 contains a heap-based buffer overflow in the set_ap_param command handled by the /localcfg endpoint. An authenticated attacker can supply oversized input, resulting in denial of service and potentially arbitrary code execution.
CVE-2026-8987
CRITICALPre-NVD 9.49.4Trending — 3 sources updated this weekElevated
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
Triggered by: NVD CVSS baseline
Sources: cna:cyberdanube
9.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.4Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.4
- EG Score
- 9.4(low)
- EPSS
- 28.1%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (1)
Auto-updated Jul 22, 2026🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available
Multiple Vulnerabilities in Autel Maxi Charger | CyberDanube
https://cyberdanube.com/security-research/multiple-vulnerabilities-in-autel-maxi-charger/Vendor Advisories for CVE-2026-8987(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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-22 14:08 UTCEPSS rescore
- 2026-07-21 23:11 UTCEG score recompute
- 2026-07-21 21:38 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-8987?
CVE-2026-8987 is a critical vulnerability published on July 21, 2026. Autel Maxi Charger Single firmware through V1.03.51 contains a heap-based buffer overflow in the setapparam command handled by the /localcfg endpoint. An authenticated attacker can supply oversized input, resulting in denial of service and potentially arbitrary code execution.
When was CVE-2026-8987 disclosed?
CVE-2026-8987 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8987 actively exploited?
CVE-2026-8987 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-8987?
CVE-2026-8987 has a CVSS v3 base score of 9.4 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-8987?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8987, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-8987
Is Your Infrastructure Affected by CVE-2026-8987?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.