Severity by source
AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Physical presence required per description; AC:H for JWT forge complexity; full C/I/A impact reflects unrestricted RCE on the embedded device.
Primary rating from Vendor (zdi).
CVSS VectorVendor: zdi
Lifecycle Timeline
1DescriptionCVE.org
Autel MaxiCharger AC Elite Home Software Update Improper Verification of Cryptographic Signature Arbitrary Code Execution Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Autel MaxiCharger AC Elite Home EV chargers. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the handling of software updates. The issue results from the lack of proper validation of a user-supplied software update image. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-29062.
AnalysisAI
Arbitrary code execution in Autel MaxiCharger AC Elite Home EV chargers is possible for physically present attackers who supply a crafted, unsigned or improperly signed firmware update image to the device. The flaw (CWE-347) stems from the absence of cryptographic signature validation during the software update process - tagged as a JWT attack vector - meaning the update mechanism accepts attacker-controlled images without verifying their authenticity. No public exploit has been identified at time of analysis, and exploitation requires physical proximity, but a successful attack achieves full code execution in the device context with high confidentiality, integrity, and availability impact.
Technical ContextAI
The affected product is the Autel MaxiCharger AC Elite Home residential EV charger, identified by CPE cpe:2.3:a:autel:maxicharger_ac_elite_home:*:*:*:*:*:*:*:* - the wildcard version field indicates all known versions are affected. The root cause is CWE-347 (Improper Verification of Cryptographic Signature), a class of vulnerability where software fails to validate the digital signature of externally supplied data before trusting and executing it. The 'JWT Attack' tag from ZDI suggests the update mechanism relies on JSON Web Tokens for image authentication or integrity binding, and the JWT validation is either absent or bypassable - allowing an attacker to substitute a malicious firmware image without triggering rejection. This is consistent with embedded/IoT update pipelines that implement ad-hoc JWT-based signing schemes susceptible to algorithm confusion, none-algorithm bypass, or missing signature enforcement.
RemediationAI
The primary remediation is to apply any firmware update released by Autel that enforces cryptographic signature validation during the update process; the exact patched firmware version has not been independently confirmed from available data - consult the ZDI advisory at https://www.zerodayinitiative.com/advisories/ZDI-26-433/ and Autel's official support channels for the specific fixed release. Until a verified patch is applied, the most effective compensating control is physical access restriction: deploy the charger in a secured location (locked enclosure, access-controlled garage, or monitored installation) so that unauthorized individuals cannot reach the update interface. If the charger exposes a USB or SD card update port, physically disable or seal that port. Additionally, establish an asset inventory of deployed MaxiCharger AC Elite Home units and monitor for unexpected firmware version changes as a detection control - tampered devices may report anomalous firmware strings. Disabling self-service firmware update capability in favor of managed, authenticated updates via a controlled backend (if supported by the device) would also reduce the attack surface.
More in Jwt Attack
View allWhy is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update
Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke
Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT
A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti
A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27
A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
cosign is a container signing and verification utility. Rated critical severity (CVSS 9.8), this vulnerability is remote
Biscuit is an authentication and authorization token for microservices architectures. Rated critical severity (CVSS 9.8)
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-50556
GHSA-mp9m-rq8w-3xm6