CVE-2026-8986

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-22. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-46640 (ENISA EUVD) · GHSA-pfm9-xrwg-mf3r (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 3.3%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (CyberDanube) lists Autel MaxiCharger Single versions up to and including V1.03.51 as affected. No release containing a fix is confirmed on record.

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.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
3.3%
EPSS %ILE
88th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
3.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 21, 2026

Last Modified

October 24, 2026

Advisory Details (1)

Auto-updated Oct 26, 2026
🔬 Proof of concept available. No fix on record yet.
Web page🟡 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 23× in last 7d / 75× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 437 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 338 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  2. 2026-10-29 14:52 UTCEG score recompute
  3. 2026-10-29 14:52 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-28 16:33 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  5. 2026-10-28 14:13 UTCEG score recompute
  6. 2026-10-28 14:13 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  8. 2026-10-27 13:14 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-26 20:49 UTCEG score recompute
  10. 2026-10-26 20:49 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  12. 2026-10-25 18:13 UTCEG score recompute
  13. 2026-10-25 18:13 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-25 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  15. 2026-10-25 13:52 UTCEG score recompute
  16. 2026-10-24 17:26 UTCEG score recompute
  17. 2026-10-24 17:26 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-24 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  19. 2026-10-24 14:33 UTCEG score recompute
  20. 2026-10-24 14:33 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-23 16:32 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  22. 2026-10-23 13:55 UTCEG score recompute
  23. 2026-10-23 13:55 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-22 16:35 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  25. 2026-10-22 13:16 UTCEG score recompute
Show 74 more
  1. 2026-10-22 13:16 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-21 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  3. 2026-10-21 12:37 UTCEG score recompute
  4. 2026-10-21 12:37 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-20 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  6. 2026-10-20 11:50 UTCEG score recompute
  7. 2026-10-20 11:50 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-19 16:33 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  9. 2026-10-19 11:12 UTCEG score recompute
  10. 2026-10-19 11:12 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-18 16:33 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  12. 2026-10-18 08:23 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-18 03:01 UTCEG score recompute
  14. 2026-10-17 16:35 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  15. 2026-10-17 07:41 UTCEG score recompute
  16. 2026-10-17 07:41 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-16 16:44 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  18. 2026-10-16 07:01 UTCEG score recompute
  19. 2026-10-16 07:01 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-15 16:33 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  21. 2026-10-15 05:46 UTCEG score recompute
  22. 2026-10-15 05:46 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-14 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  24. 2026-10-14 01:23 UTCEG score recompute
  25. 2026-10-14 01:23 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-13 16:35 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  27. 2026-10-12 21:36 UTCEG score recompute
  28. 2026-10-12 21:36 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-12 16:35 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  30. 2026-10-12 14:48 UTCEG score recompute
  31. 2026-10-12 05:09 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-11 19:14 UTCEG score recompute
  33. 2026-10-11 16:31 UTCEG score recompute
  34. 2026-10-11 13:50 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  35. 2026-10-11 13:47 UTCEG score recompute
  36. 2026-10-10 20:00 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  37. 2026-10-09 20:08 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  38. 2026-10-08 17:13 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  39. 2026-10-07 23:48 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  40. 2026-10-06 15:18 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  41. 2026-10-05 17:44 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  42. 2026-10-04 23:22 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  43. 2026-10-04 14:46 UTCEG score recompute
  44. 2026-10-04 14:46 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-01 19:51 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  46. 2026-10-01 15:53 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-01 11:29 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-01 07:25 UTCEG score recompute
  49. 2026-10-01 07:25 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-09-30 15:04 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  51. 2026-09-28 13:52 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  52. 2026-09-28 10:24 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-09-28 06:04 UTCEG score recompute
  54. 2026-09-28 06:04 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-09-27 13:49 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  56. 2026-09-26 15:59 UTCEPSS rescoreEPSS 3.3% · 88th percentile
  57. 2026-09-24 14:04 UTCEPSS rescoreEPSS 3.3% · 87th percentile
  58. 2026-09-24 13:07 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-09-24 08:16 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-24 03:20 UTCEG score recompute
  61. 2026-09-24 03:20 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-23 17:54 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  63. 2026-09-23 09:26 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-23 05:24 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-23 01:22 UTCEG score recompute
  66. 2026-09-23 01:22 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-09-22 16:01 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  68. 2026-09-21 21:09 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  69. 2026-09-20 20:16 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  70. 2026-09-20 05:54 UTCEG score recompute
  71. 2026-09-20 05:54 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-19 00:19 UTCEG score recompute
  73. 2026-09-19 00:19 UTCGHSA enrichmentGHSA-pfm9-xrwg-mf3r · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-18 19:28 UTCEPSS rescoreEPSS 2.3% · 82nd percentile

Frequently asked(5)

What is CVE-2026-8986?
CVE-2026-8986 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-8986 published?
The CVE record for CVE-2026-8986 was published on July 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-8986 actively exploited?
CVE-2026-8986 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8986?
CVE-2026-8986 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-8986?
No fix for CVE-2026-8986 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (CyberDanube) lists Autel MaxiCharger Single versions up to and including V1.03.51 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-8986 are linked in the Vendor Advisories panel on this page.

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.