CVE-2025-5827
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 Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Autel MaxiCharger AC Wallbox Commercial EV chargers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the ble_process_esp32_msg function. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-26369.
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 confidenceStack-based buffer overflow in the ble_process_esp32_msg function allows remote attackers to execute arbitrary code by sending specially crafted BLE messages with unchecked length data to the fixed-length stack buffer, without requiring authentication.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/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.
-
Identify the Autel MaxiCharger modelLocate the device label or check the administrative web interface or mobile app for the exact model number (e.g., AC Elite Business C50, AC Pro, AC Ultra, DC Compact Mobile, DC Compact Pedestal, DC Fast, DC Hipower, DH480)Affected if The model is any of the listed affected products
-
Check the installed firmware versionAccess the charger via its web interface, mobile app, or OLED display (if equipped) and navigate to the firmware or version information section. Compare the displayed version against the affected ranges: versions below 1.39.51 or below 1.56.51Affected if The firmware version is less than 1.39.51 or less than 1.56.51 (the exact threshold depends on the specific model and update branch)
-
Verify if BLE is enabledCheck the device configuration settings via the web interface, mobile app, or device settings menu for Bluetooth Low Energy status. If accessible, examine BLE advertising and connection availability from a nearby BLE-enabled deviceAffected if BLE is actively enabled and accepting connections - the vulnerability is only exploitable when BLE is operational
-
Confirm network accessibility to BLE interfaceDetermine whether the device BLE interface is reachable from untrusted network segments. This may involve checking physical proximity (BLE range is typically limited to ~10-30 meters) or whether the charger is exposed beyond the expected operational areaAffected if The BLE interface is accessible to unauthenticated, network-adjacent attackers (within BLE range)
You are affected if your Autel MaxiCharger device is running firmware version less than 1.39.51 or less than 1.56.51 AND BLE is currently enabled and accessible.
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
Isolate EV chargers on dedicated network segments; disable BLE if not required; implement compensating controls until vendor firmware patch is available; monitor for unauthorized BLE devices in the vicinity.
Upgrade to firmware version 1.39.51 or later (1.x branch) OR version 1.56.51 or later (2.x branch)
- 1. Identify the current firmware version of the affected Autel MaxiCharger device through the device management interface or console.
- 2. Determine which firmware branch your device is running (1.x or 2.x series) to select the appropriate fixed version.
- 3. Download the firmware update from the official Autel Energy support portal or through your device management system.
- 4. Follow the manufacturer's standard firmware upgrade procedure, typically via the web interface, mobile app, or OTA update mechanism.
- 5. After upgrading, verify the firmware version has been updated to 1.39.51 or higher (for the 1.x branch) or 1.56.51 or higher (for the 2.x branch).
- 6. Confirm the ble_process_esp32_msg function is no longer exposed or validate the vulnerability has been addressed through testing.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5827 — 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-5827 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