CVE-2026-8986
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAutel 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAutel Maxi Charger Single firmware through V1.03.51 contains an OS command injection vulnerability in the OCPP GetDiagnostics handler. The diagnostics URL parameter is not properly sanitized before being passed to a system call, allowing an authenticated or man-in-the-middle attacker controlling the OCPP server to execute arbitrary commands on the charging station with root or elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.03.51CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the device firmware versionAccess the Autel Maxi Charger admin interface or use the device's diagnostic menu to retrieve the current firmware version. This is typically found under System Info, About, or Maintenance settings.Affected if The installed firmware version is lower than V1.03.51 (for example, V1.03.50, V1.02.x, or earlier)
-
Verify OCPP is enabledLocate the OCPP configuration settings in the charging station admin panel. OCPP is typically configured under Network Settings, Communication Protocols, or OCPP Settings.Affected if OCPP support is enabled and the station is configured to connect to an OCPP server
-
Inspect OCPP server connection settingsReview the OCPP server URL or endpoint configuration in the charging station. This defines which OCPP server the station communicates with for operations like diagnostics retrieval.Affected if The station is configured to connect to an untrusted or externally accessible OCPP server, or no server whitelist is enforced
-
Check GetDiagnostics handler configurationLook for GetDiagnostics or diagnostic retrieval settings within the OCPP module configuration. This feature allows the station to send diagnostic logs to a configured OCPP server.Affected if GetDiagnostics functionality is available and the station can initiate diagnostics retrieval to a remote server
The environment is affected if the Autel Maxi Charger firmware is below V1.03.51 AND OCPP with GetDiagnostics is enabled, allowing the station to contact a potentially malicious OCPP server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate firmware to a version beyond V1.03.51 when available, and restrict OCPP server connections to only trusted, authorized servers to prevent malicious server injection.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8986 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8986 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data