CVE-2026-8985

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 4.2%, top 10% 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
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS: 10.0Exploit: 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 in the /test endpoint exposed on TCP port 9002. An unauthenticated attacker can supply crafted input in the url parameter to execute arbitrary operating system commands.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
76(Attend)
EG Risk 76/100SSVC: Attend

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
Severity100% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
4%
EPSS %ILE
90%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jul 29, 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-8985(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 55× in last 7d / 64× 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 20:01 UTCGHSA enrichment
  2. 2026-08-01 16:08 UTCGHSA enrichment
  3. 2026-08-01 12:15 UTCGHSA enrichment
  4. 2026-08-01 08:22 UTCGHSA enrichment
  5. 2026-08-01 04:29 UTCEG score recompute
  6. 2026-08-01 04:29 UTCGHSA enrichment
  7. 2026-08-01 04:16 UTCEPSS rescore
  8. 2026-08-01 00:35 UTCGHSA enrichment
  9. 2026-07-31 20:39 UTCGHSA enrichment
  10. 2026-07-31 16:46 UTCGHSA enrichment
  11. 2026-07-31 12:53 UTCGHSA enrichment
  12. 2026-07-31 08:58 UTCGHSA enrichment
  13. 2026-07-31 05:06 UTCGHSA enrichment
  14. 2026-07-31 01:10 UTCGHSA enrichment
  15. 2026-07-30 21:18 UTCEG score recompute
  16. 2026-07-30 21:18 UTCGHSA enrichment
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 16:07 UTCGHSA enrichment
  19. 2026-07-30 12:14 UTCEG score recompute
  20. 2026-07-30 12:14 UTCGHSA enrichment
  21. 2026-07-30 08:21 UTCGHSA enrichment
  22. 2026-07-30 04:28 UTCEG score recompute
  23. 2026-07-30 04:28 UTCGHSA enrichment
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-30 00:35 UTCGHSA enrichment
Show 39 more
  1. 2026-07-29 20:41 UTCGHSA enrichment
  2. 2026-07-29 16:27 UTCGHSA enrichment
  3. 2026-07-29 12:30 UTCGHSA enrichment
  4. 2026-07-29 08:37 UTCGHSA enrichment
  5. 2026-07-29 04:42 UTCGHSA enrichment
  6. 2026-07-29 00:49 UTCGHSA enrichment
  7. 2026-07-28 20:55 UTCGHSA enrichment
  8. 2026-07-28 17:02 UTCEG score recompute
  9. 2026-07-28 17:02 UTCGHSA enrichment
  10. 2026-07-28 15:37 UTCEPSS rescore
  11. 2026-07-28 12:52 UTCGHSA enrichment
  12. 2026-07-28 09:00 UTCGHSA enrichment
  13. 2026-07-28 05:04 UTCGHSA enrichment
  14. 2026-07-28 01:09 UTCGHSA enrichment
  15. 2026-07-27 21:16 UTCGHSA enrichment
  16. 2026-07-27 17:24 UTCEG score recompute
  17. 2026-07-27 17:24 UTCGHSA enrichment
  18. 2026-07-27 14:14 UTCEPSS rescore
  19. 2026-07-27 13:31 UTCGHSA enrichment
  20. 2026-07-27 09:31 UTCGHSA enrichment
  21. 2026-07-27 05:38 UTCGHSA enrichment
  22. 2026-07-27 01:31 UTCGHSA enrichment
  23. 2026-07-26 21:38 UTCGHSA enrichment
  24. 2026-07-26 17:44 UTCEG score recompute
  25. 2026-07-26 17:44 UTCGHSA enrichment
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-26 13:51 UTCEG score recompute
  28. 2026-07-26 13:51 UTCGHSA enrichment
  29. 2026-07-26 09:58 UTCEG score recompute
  30. 2026-07-26 09:58 UTCGHSA enrichment
  31. 2026-07-25 14:18 UTCEPSS rescore
  32. 2026-07-24 14:18 UTCEPSS rescore
  33. 2026-07-23 14:18 UTCEPSS rescore
  34. 2026-07-23 03:23 UTCEG score recompute
  35. 2026-07-22 22:56 UTCEG score recompute
  36. 2026-07-22 22:56 UTCGHSA enrichment
  37. 2026-07-22 14:08 UTCEPSS rescore
  38. 2026-07-21 23:11 UTCEG score recompute
  39. 2026-07-21 21:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8985?
CVE-2026-8985 is a critical vulnerability published on July 21, 2026. Autel Maxi Charger Single firmware through V1.03.51 is vulnerable to OS command injection in the /test endpoint exposed on TCP port 9002. An unauthenticated attacker can supply crafted input in the url parameter to execute arbitrary operating system commands.
When was CVE-2026-8985 disclosed?
CVE-2026-8985 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-8985 actively exploited?
CVE-2026-8985 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 10.1% of all scored CVEs.
What is the CVSS score of CVE-2026-8985?
CVE-2026-8985 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-8985?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8985, 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-8985

Explore →

Is Your Infrastructure Affected by CVE-2026-8985?

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

Start Free Scan →Browse All CVEs