Skip to main content

Autel MaxiCharger EUVDEUVD-2026-46437

| CVE-2026-8988 HIGH
On-Chip Debug and Test Interface With Improper Access Control (CWE-1191)
2026-07-21 CyberDanube GHSA-qpg5-v459-hjvj
8.6
CVSS 4.0 · Vendor: CyberDanube
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain physical access to charger
  2. Delivery
    Connect to exposed UART header
  3. Exploit
    Interrupt U-Boot autoboot
  4. Execution
    Modify boot args/filesystem
  5. Persist
    Boot to root shell
  6. Impact
    Full OS compromise / persistent implant

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture On-chip debug access control
Exploitation Conditions

Exploitation requires direct physical access to the charger's circuit board and the exposed, unauthenticated UART/serial interface, plus the ability to interrupt U-Boot's autoboot sequence (the bootloader must permit boot interruption, which it does on firmware through V1.03.51). No credentials, no user interaction, and no network connectivity are needed once the attacker is at the serial console. Limiting factors: the attack cannot be performed remotely (AV:P) - the attacker must be on-site and typically must open the enclosure to reach the UART header - and it is confined to devices running firmware V1.03.51 or earlier; enclosure tampering may be detectable and physical siting/monitoring can materially raise the difficulty.

Impact

The vendor CVSS 4.0 score of 8.6 (High) is driven by a full high impact to confidentiality, integrity and availability of both the vulnerable charger and subsequent systems (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H) combined with low attack complexity and no privilege or user-interaction requirement. The single most important tempering factor is the physical attack vector (AV:P): an attacker must be physically present at the device and open/access the board to reach the UART header. There is no EPSS score, KEV listing, or SSVC decision data provided, so automated/remote exploitation probability cannot be quantified - but note that EPSS/KEV are largely irrelevant here because the flaw is not network-reachable and therefore not amenable to mass, automated exploitation. This is a real risk for the specific threat model of tampering, roadside/kerbside, or supply-chain physical attacks on unattended charging hardware, rather than a remote internet-facing emergency. Public exploit code exists, lowering the skill barrier for anyone who does obtain physical access. Note: the tags label this 'Information Disclosure,' but the description and CVSS integrity/availability impacts indicate full device takeover, not merely data disclosure - the tag understates the impact.

Exploit ScenarioDerived

An attacker with brief physical access to a publicly sited MaxiCharger Single opens the enclosure, connects a USB-to-serial adapter to the exposed UART header, and interrupts the boot countdown to reach the U-Boot prompt. Using the publicly available exploit method, they modify the kernel command line or root filesystem to spawn a root shell, obtaining full OS access to read stored credentials/certificates, alter charging or billing logic, or implant persistent malicious firmware.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 21, 2026

Physical compromise of Autel MaxiCharger Single EV charging stations running firmware through V1.03.51 is possible via an unprotected UART interface that lets an attacker halt boot and drop into the U-Boot bootloader. From the bootloader an attacker can rewrite boot configuration or the filesystem to gain full operating-system access on the charger. Publicly available exploit code exists (published by CyberDanube), though there is no public exploit identified as being used in active attacks and the flaw requires physical access.

RemediationAI

No vendor-released patch version is identified at time of analysis, so remediation centers on physical and boot-chain hardening: consult the CyberDanube advisory (https://cyberdanube.com/security-research/multiple-vulnerabilities-in-autel-maxi-charger/) and Autel for firmware updates, and apply any fixed firmware once released. As compensating controls, disable or password-protect the U-Boot console (set a CONFIG_AUTOBOOT_KEYED/bootstop password and non-interruptible boot delay) so the boot sequence cannot be halted from serial; physically block or remove the exposed UART header and use tamper-evident enclosures or security screws to detect and deter case opening; and restrict physical access to the charging unit's internal board (locked enclosures, siting in monitored/CCTV-covered locations). The trade-off of locking the U-Boot console is loss of field-debug/recovery convenience for technicians, and tamper enclosures add servicing overhead - but these are the only meaningful mitigations for a physical UART/bootloader flaw until patched firmware is available.

Affected VersionsENISA

MaxiCharger Single 0 ≤V1.03.51

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the embedded Linux/U-Boot boot chain on the Autel MaxiCharger Single, an AC/DC electric-vehicle charging station (CPE cpe:2.3:a:autel:maxicharger_single). The root cause is CWE-1191 (exposed on-chip debug/test interface with improper access control): a serial UART console remains active and unauthenticated on the board, and U-Boot is configured to allow interruption of the automatic boot sequence (typically by sending a keystroke during the countdown). Because U-Boot runs before any OS-level access controls, an attacker at the console can alter kernel boot arguments (e.g., inject an init=/bin/sh or single-user parameter), load alternative images, or mount and modify the root filesystem, bypassing whatever authentication the running firmware would normally enforce.

Know when Maxicharger Single gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (CyberDanube) PRIMARY 8.6 HIGH
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
vuln.today AI 7.6 HIGH

Physical UART access with no auth or interaction (AV:P/PR:N/UI:N); bootloader compromise crosses from boot to OS trust boundary giving S:C and full C/I/A:H.

3.1 AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (CyberDanube).

CVSS VectorVendor: CyberDanube

Attack Vector
Physical
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

Autel Maxi Charger Single firmware through V1.03.51 exposes an accessible UART interface that permits interruption of the boot process and access to the U-Boot bootloader. An attacker with physical access can modify the boot configuration or file system to obtain operating system access.

Executive ViewAI

Why It Matters

Autel MaxiCharger Single charging stations are exposed to complete operating system compromise if an attacker gains physical access to the device hardware. With publicly available exploit code and no vendor patch currently available, this creates an integrity and availability risk for the organization's EV charging infrastructure that must be managed through interim physical security controls.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: enforce strict physical access controls through facility locks, camera surveillance, and tamper-evident seals at all affected charging station locations; establish and enforce maintenance access protocols requiring personnel identification and documented authorization; implement incident response procedures for suspected physical tampering or unauthorized access attempts; audit and log all hardware maintenance activities and modifications; and consider operational suspension or equipment replacement for stations supporting critical charging operations where physical security controls are insufficient.

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
Low
single vendor EV-charger model, niche industry-specific hardware footprint
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

63
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy