Skip to main content

Autel MaxiCharger EUVDEUVD-2026-50558

| CVE-2026-13309 MEDIUM
Stack-based Buffer Overflow (CWE-121)
2026-07-29 zdi GHSA-hhjf-qv52-vp59
6.8
CVSS 3.0 · Vendor: zdi
View

Attack ChainAIDerived

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

  1. Access
    Gain physical proximity to charger
  2. Delivery
    Present crafted NFC card to reader
  3. Exploit
    Trigger stack buffer overflow in NFC response handler
  4. Execution
    Overwrite return address on stack
  5. Impact
    Execute arbitrary code in device firmware context

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Physical presence within NFC read range (typically under 10 cm) of the charger is mandatory - remote or network-based exploitation is not possible given AV:P. The NFC card interface must be active and accessible on the device, which is a default operational state for this product. No authentication to the charger is required before the vulnerable code path is triggered, as the overflow occurs during card response processing prior to any authentication outcome. Exploitation is limited to attackers who can physically access the device without raising alarm; for chargers in monitored or access-controlled environments this is a meaningful barrier. The wildcard CPE suggests no firmware version is exempt, but this has not been confirmed by the vendor - specific firmware versions may include mitigations not reflected in the NVD entry.

Impact

The CVSS 3.0 base score of 6.8 accurately reflects a constrained but severe vulnerability: AV:P (physical access) is the primary limiting factor, while the impact triad of C:H/I:H/A:H indicates full device compromise if exploited. Real-world risk is geographically and logistically bounded - an attacker must stand within NFC range (typically under 10 cm) of a deployed charger with a crafted card, making remote or internet-scale exploitation impossible. This is not a KEV-listed vulnerability, and no EPSS data was provided in the source intelligence, making probabilistic exploitation forecasting unavailable. For targets of concern - such as chargers in publicly accessible locations (parking garages, fleet depots, commercial properties) - the physical access barrier is lower than it would appear for enterprise IT assets. Compromise of the device firmware could enable persistent tampering, billing fraud, credential harvesting from NFC card data, or lateral movement into the charging network infrastructure if the device has network connectivity. The wildcard CPE version string suggests all firmware versions are affected, but no vendor-confirmed version boundary is available.

Exploit ScenarioDerived

An attacker approaches a publicly accessible Autel MaxiCharger AC Elite Home unit - for example, in a parking garage or commercial charging station - and presents a specially crafted NFC card to the charger's reader. The malformed card response triggers a stack buffer overflow in the NFC handling firmware, overwriting the return address and redirecting execution to attacker-supplied shellcode embedded in the card payload. No public proof-of-concept exploit code has been identified, but the ZDI disclosure and precise technical description (fixed-length stack buffer, crafted card response) provide sufficient detail for capable researchers to develop one.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jul 29, 2026

Stack-based buffer overflow in the NFC card response handler of Autel MaxiCharger AC Elite Home EV chargers enables arbitrary code execution by a physically present attacker. The device's NFC interface fails to enforce bounds on a fixed-length stack buffer when processing card responses, allowing a maliciously crafted NFC card to overwrite stack memory and redirect execution flow to attacker-controlled code. No authentication is required to trigger the flaw - proximity to the device and a crafted NFC card are the sole prerequisites. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

RemediationAI

No vendor-released patch with an exact fix version has been identified in the available data. Operators should consult the Autel vendor advisory directly and the ZDI disclosure at https://www.zerodayinitiative.com/advisories/ZDI-26-435/ for patch availability updates. As a compensating control, restrict physical access to deployed MaxiCharger AC Elite Home units: locate chargers in controlled-access areas where unaccompanied public proximity is not possible, such as gated parking or monitored enclosures - this directly eliminates the physical (AV:P) attack vector. If the device supports disabling or restricting NFC card authentication in favor of alternative authentication methods (e.g., app-based or network-side authentication only), evaluate that configuration change; note this may affect user experience and interoperability with NFC-based fleet cards. Monitor ZDI and Autel security advisories for firmware updates, as the ZDI coordinated disclosure process typically results in vendor-patched releases.

Affected VersionsENISA

MaxiCharger AC Elite Home 1.39.51

Affected Packages

euvd maxicharger_ac_elite_home no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

The affected product is the Autel MaxiCharger AC Elite Home, an EV charging station that supports NFC-based card authentication (CPE: cpe:2.3:a:autel:maxicharger_ac_elite_home:*:*:*:*:*:*:*:*). The vulnerability is rooted in CWE-121 (Stack-based Buffer Overflow): when the device firmware processes a response from an NFC card presented at the reader interface, it copies card-supplied data into a fixed-length stack buffer without validating the response length. An oversized or specially structured card response overwrites the stack frame, potentially clobbering the saved return address or function pointers. Because NFC card interactions occur before any authentication handshake is completed, no credential or prior access is needed. The vulnerability was discovered and reported by Trend Micro's Zero Day Initiative under internal tracker ZDI-CAN-29044, publicly disclosed as ZDI-26-435.

Know when Maxicharger Ac Elite Home 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 (zdi) PRIMARY 6.8 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 6.8 MEDIUM

Physical access required to reach NFC reader; no authentication needed before overflow; full device compromise on success, no scope change.

3.1 AV:P/AC:L/PR:N/UI:N/S:U/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:N/SI:N/SA:N

Primary rating from Vendor (zdi).

CVSS VectorVendor: zdi

Attack Vector
Physical
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Autel MaxiCharger AC Elite Home NFC Stack-based Buffer Overflow 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 card responses via the NFC interface. A crafted card response can trigger an overflow of a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-29044.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Low
consumer/prosumer EV charger with limited commercial deployment footprint
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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

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

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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