CVE-2026-8986

CRITICALPre-NVD 9.59.5—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.2%, top 34% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
9.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Autel Maxi Charger Single firmware through V1.03.51 is vulnerable to OS command injection when processing OCPP GetDiagnostics requests. A malicious or compromised OCPP server can supply a crafted diagnostics URL that results in arbitrary command execution on the charging station.

CVSS v3
9.5
EG Score
9.5(medium)
EG Risk
59(Track*)
EG Risk 59/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 computed
Severity95% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
66%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jul 31, 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-8986(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 51× in last 7d / 60× 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.

  1. 2026-08-01 18:18 UTCGHSA enrichment
  2. 2026-08-01 14:16 UTCGHSA enrichment
  3. 2026-08-01 10:14 UTCGHSA enrichment
  4. 2026-08-01 06:12 UTCEG score recompute
  5. 2026-08-01 06:12 UTCGHSA enrichment
  6. 2026-08-01 04:16 UTCEPSS rescore
  7. 2026-08-01 02:08 UTCGHSA enrichment
  8. 2026-07-31 22:05 UTCGHSA enrichment
  9. 2026-07-31 18:00 UTCGHSA enrichment
  10. 2026-07-31 13:54 UTCGHSA enrichment
  11. 2026-07-31 09:52 UTCGHSA enrichment
  12. 2026-07-31 05:46 UTCGHSA enrichment
  13. 2026-07-31 01:44 UTCGHSA enrichment
  14. 2026-07-30 21:39 UTCGHSA enrichment
  15. 2026-07-30 17:33 UTCEG score recompute
  16. 2026-07-30 17:33 UTCGHSA enrichment
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 13:30 UTCGHSA enrichment
  19. 2026-07-30 09:27 UTCEG score recompute
  20. 2026-07-30 09:27 UTCGHSA enrichment
  21. 2026-07-30 05:25 UTCEG score recompute
  22. 2026-07-30 05:25 UTCGHSA enrichment
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-30 01:21 UTCGHSA enrichment
  25. 2026-07-29 21:18 UTCGHSA enrichment
Show 35 more
  1. 2026-07-29 17:15 UTCGHSA enrichment
  2. 2026-07-29 13:13 UTCGHSA enrichment
  3. 2026-07-29 09:11 UTCGHSA enrichment
  4. 2026-07-29 05:08 UTCGHSA enrichment
  5. 2026-07-29 01:05 UTCGHSA enrichment
  6. 2026-07-28 21:04 UTCGHSA enrichment
  7. 2026-07-28 17:02 UTCEG score recompute
  8. 2026-07-28 17:02 UTCGHSA enrichment
  9. 2026-07-28 15:37 UTCEPSS rescore
  10. 2026-07-28 11:40 UTCGHSA enrichment
  11. 2026-07-28 07:36 UTCGHSA enrichment
  12. 2026-07-28 03:31 UTCGHSA enrichment
  13. 2026-07-27 23:29 UTCGHSA enrichment
  14. 2026-07-27 19:15 UTCGHSA enrichment
  15. 2026-07-27 15:11 UTCGHSA enrichment
  16. 2026-07-27 10:38 UTCGHSA enrichment
  17. 2026-07-27 06:34 UTCGHSA enrichment
  18. 2026-07-27 02:31 UTCGHSA enrichment
  19. 2026-07-26 22:26 UTCGHSA enrichment
  20. 2026-07-26 18:24 UTCEG score recompute
  21. 2026-07-26 18:23 UTCGHSA enrichment
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 14:02 UTCEG score recompute
  24. 2026-07-26 14:01 UTCGHSA enrichment
  25. 2026-07-26 09:58 UTCEG score recompute
  26. 2026-07-26 09:58 UTCGHSA enrichment
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-24 14:18 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 03:23 UTCEG score recompute
  31. 2026-07-22 22:56 UTCEG score recompute
  32. 2026-07-22 22:56 UTCGHSA enrichment
  33. 2026-07-22 14:08 UTCEPSS rescore
  34. 2026-07-21 23:11 UTCEG score recompute
  35. 2026-07-21 21:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8986?
CVE-2026-8986 is a critical vulnerability published on July 21, 2026. Autel Maxi Charger Single firmware through V1.03.51 is vulnerable to OS command injection when processing OCPP GetDiagnostics requests. A malicious or compromised OCPP server can supply a crafted diagnostics URL that results in arbitrary command execution on the charging station.
When was CVE-2026-8986 disclosed?
CVE-2026-8986 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-8986 actively exploited?
CVE-2026-8986 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 34.5% of all scored CVEs.
What is the CVSS score of CVE-2026-8986?
CVE-2026-8986 has a CVSS v3 base score of 9.5 (NVD).
How do I remediate CVE-2026-8986?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8986, 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-8986

Explore →

Is Your Infrastructure Affected by CVE-2026-8986?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs