CVE-2025-5826
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 MaxiCharger AC Wallbox Commercial ble_process_esp32_msg Misinterpretation of Input Vulnerability. This vulnerability allows network-adjacent attackers to inject arbitrary AT commands on affected installations of Autel MaxiCharger AC Wallbox Commercial charging stations. Authentication is not required to exploit this vulnerability. The specific flaw exists within the ble_process_esp32_msg function. The issue results from misinterpretation of input data. An attacker can leverage this vulnerability to execute AT commands in the context of the device. Was ZDI-CAN-26368.
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 confidenceThe Autel MaxiCharger AC Wallbox Commercial charging station contains a vulnerability in its Bluetooth Low Energy (BLE) communication handler. The ble_process_esp32_msg function fails to properly validate incoming BLE data, allowing an adjacent attacker to inject arbitrary AT commands that execute on the embedded ESP32 microcontroller. No authentication is required, and exploitation occurs within BLE communication range.
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.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify the Autel MaxiCharger modelInspect the device label, packaging, or administrative web interface to confirm the exact model number (e.g., AC Elite Business C50, AC Pro, AC Ultra, DC Compact Mobile, DC Compact Pedestal, DC Fast, DC Hipower, or DH480).Affected if The device is any of the listed Autel MaxiCharger models.
-
Determine the installed firmware versionAccess the device administrative interface or use the vendor-supplied mobile/desktop application to retrieve the current firmware version. Alternatively, check the device status screen or firmware update log.Affected if The firmware version is below 1.39.51 or below 1.56.51 (note: some product lines use different version numbering schemes).
-
Confirm BLE is enabledCheck the device configuration settings via the administrative interface or mobile application to verify whether Bluetooth Low Energy communication is turned on.Affected if BLE is enabled and the firmware version is in the affected range.
-
Verify BLE exposure scopeReview network segmentation and physical access controls to determine if the device BLE interface is accessible to unauthorized adjacent attackers.Affected if The device BLE interface is reachable by non-authorized devices within BLE communication range.
The environment is affected if the device is an Autel MaxiCharger from the listed models, runs firmware version lower than 1.39.51 or lower than 1.56.51, and has BLE enabled.
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.
dbcve · scoped1.39.511.56.51
Apply vendor firmware patch when available; until then, restrict BLE exposure through network segmentation, disable BLE if not operationally required, and monitor for unauthorized BLE device proximity.
Firmware version 1.39.51 or 1.56.51 (or later)
- Identify the current firmware version of the MaxiCharger device via the device admin interface or console
- Download the firmware update from Autel's official support portal (www.autelenergy.com)
- Backup current device configuration if possible
- Ensure the device is powered and connected via Ethernet during firmware update to prevent interruption
- Upload and apply firmware version 1.39.51 or 1.56.51 (or later) via the device's web interface or management system
- Verify the firmware version was successfully applied and the device operates normally
- After update, confirm the ble_process_esp32_msg function no longer accepts unauthorized AT commands
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5826 — 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-2025-5826 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