Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-5828 Overview
CVE-2025-5828 is a buffer overflow vulnerability affecting Autel MaxiCharger electric vehicle (EV) chargers. The flaw resides in the handling of USB frame packets, specifically the wLength field. The firmware fails to validate the length of user-supplied data before copying it into a fixed-length buffer, enabling memory corruption. An attacker with physical access to a vulnerable charger can execute arbitrary code in the context of the device. Authentication is not required. The issue was reported through the Zero Day Initiative as ZDI-CAN-26328 and tracked publicly as advisory ZDI-25-347. The weakness is classified under CWE-120 (Classic Buffer Overflow).
Critical Impact
A physically present attacker can gain code execution on affected Autel MaxiCharger EV chargers without authentication, compromising charger integrity, availability, and any processed data.
Affected Products
- Autel MaxiCharger AC Elite Business C50, AC Pro, and AC Ultra (American and European standard firmware)
- Autel MaxiCharger DC Compact Mobile, DC Compact Pedestal, DC Fast, and DC HiPower
- Autel MaxiCharger DH480 and MaxiCharger Single Charger
Discovery Timeline
- 2025-06-25 - CVE-2025-5828 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-5828
Vulnerability Analysis
The vulnerability affects the USB communication stack used by Autel MaxiCharger firmware. During USB frame processing, the device reads a length field (wLength) supplied by the connected host and uses it as the copy length when writing packet data into a fixed-size stack or heap buffer. Because no bounds check is performed against the destination buffer size, oversized payloads overwrite adjacent memory. The classic buffer overflow pattern [CWE-120] allows the attacker to corrupt return addresses, function pointers, or control structures, achieving arbitrary code execution on the charger's embedded processor. Successful exploitation yields full control over charger logic, including power delivery, billing data, and network communications with backend management platforms.
Root Cause
The root cause is missing input validation on the wLength field of USB setup packets prior to a memory copy into a fixed-length buffer. The firmware trusts attacker-controlled length metadata without comparing it to the destination buffer size.
Attack Vector
Exploitation requires physical access to the charger's USB interface. The attacker connects a crafted USB device or host to the charger and sends a malformed USB frame with an oversized wLength value and payload. No authentication, user interaction, or network connectivity is required. See the Zero Day Initiative Advisory ZDI-25-347 for additional technical context.
// No verified exploit code is publicly available.
// Refer to ZDI-25-347 for responsible disclosure details.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2025-5828
Indicators of Compromise
- Unexpected USB devices connected to MaxiCharger units at public or fleet charging sites
- Charger reboots, service crashes, or firmware integrity failures after physical interaction with the unit
- Deviations in charger telemetry, firmware version strings, or backend heartbeat behavior following site visits
Detection Strategies
- Review physical security logs and CCTV footage covering charger enclosures for unauthorized access to USB ports
- Correlate charger-side anomalies (crash dumps, watchdog resets) with site access events through central EV charger management platforms
- Monitor backend command-and-control channels for anomalous messages originating from previously benign chargers
Monitoring Recommendations
- Enable and centrally collect diagnostic logs from the Autel backend to flag firmware integrity, boot, and USB subsystem events
- Alert on firmware hash mismatches or unexpected configuration changes reported by chargers
- Track physical tampering sensors or enclosure-open events where supported by the hardware
How to Mitigate CVE-2025-5828
Immediate Actions Required
- Inventory all deployed Autel MaxiCharger models listed in the affected products section and identify firmware variants in use
- Restrict and physically secure access to charger USB ports using lockable enclosures, tamper-evident seals, or port blockers
- Contact Autel support to obtain the latest firmware addressing CVE-2025-5828 and schedule deployment across the fleet
Patch Information
Autel has not published a vendor advisory URL in the referenced CVE data. Operators should consult Autel directly and the Zero Day Initiative Advisory ZDI-25-347 for remediation status. Apply the vendor-supplied firmware update across all affected AC and DC MaxiCharger models once available.
Workarounds
- Physically block or disable the USB interface on affected chargers using port locks or epoxy where operationally acceptable
- Deploy chargers in monitored, access-controlled locations and increase physical inspection frequency
- Limit third-party technician access and verify technician identity before any on-site maintenance involving USB connectivity
# No software configuration workaround is available.
# Mitigation requires vendor firmware updates and physical access controls on charger USB ports.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

