CVE-2025-5829
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 autocharge Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected affected installations of Autel MaxiCharger AC Wallbox Commercial EV chargers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of JSON messages. 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-26330.
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 Autel MaxiCharger AC Wallbox Commercial EV chargers during JSON message handling. The vulnerability stems from insufficient validation of user-supplied data length before copying into a fixed-size stack buffer, enabling remote code execution in the device context. Physical proximity is required for exploitation but no authentication is needed.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/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 MaxiCharger modelLocate the model label on the device physical label or check the device management interface 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, or DH480)Affected if The model is any of these eight MaxiCharger variants
-
Determine the installed firmware versionAccess the device admin interface or check system information via the device console or built-in display. Look for firmware version information under System Settings or Device InfoAffected if The firmware version is below 1.39.51 or below 1.56.51 (refer to the specific version branch for your model)
-
Confirm JSON message handling is accessibleVerify the device network service that processes JSON messages is reachable. This is typically the charging station management API accessible via the device web interface or open network portAffected if JSON message handling interface is exposed and network-accessible
The device is affected if it is any listed Autel MaxiCharger model AND the firmware version falls below 1.39.51 or below 1.56.51 (depending on the version branch), with the JSON handling interface 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
Apply vendor firmware patches when available. Prioritize physical security of charging stations and implement network segmentation to limit exposure. If no patch exists, consider compensating controls such as restricting network access to charging infrastructure.
Firmware version 1.39.51 or later, or alternatively version 1.56.51 or later (depending on which firmware branch is applicable to your device model)
- 1. Identify the current firmware version of the MaxiCharger device through its web interface or admin panel
- 2. Navigate to Autel Energy's official support or downloads page to obtain the firmware update
- 3. Download firmware version 1.39.51 or later (or 1.56.51 or later) that corresponds to your device model
- 4. Apply the firmware update using the device's admin interface or the manufacturer's recommended update procedure
- 5. After updating, verify the firmware version has been successfully changed to a version >= 1.39.51 or >= 1.56.51
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5829 — 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-5829 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