EUVD-2026-16199Severity by source
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
6DescriptionGitHub Advisory
EVerest is an EV charging software stack. Prior to version 2026.02.0, stack-based buffer overflow in CAN interface initialization: passing an interface name longer than IFNAMSIZ (16) to CAN open routines overflows ifreq.ifr_name, corrupting adjacent stack data and enabling potential code execution. A malicious or misconfigured interface name can trigger this before any privilege checks. Version 2026.02.0 contains a patch.
AnalysisAI
Stack-based buffer overflow in EVerest EV charging software allows unauthenticated local attackers to execute arbitrary code via overly long CAN interface names during initialization. The vulnerability (CWE-121) affects everest-core versions prior to 2026.02.0 with CVSS 8.4 (High severity). Proof-of-concept exploit code exists according to SSVC assessment, and the flaw triggers before privilege checks, enabling attack with no user privileges required. The vulnerability is tracked as EUVD-2026-16199 by ENISA.
Technical ContextAI
This vulnerability affects EVerest (everest-core), an open-source software stack for electric vehicle charging infrastructure, identified by CPE cpe:2.3:a:everest:everest-core:*:*:*:*:*:*:*:*. The flaw is a classic stack-based buffer overflow (CWE-121) occurring in the CAN (Controller Area Network) interface initialization routines. When opening CAN interfaces, the code copies user-supplied interface names into the ifreq.ifr_name structure field without validating that the length does not exceed IFNAMSIZ (16 bytes). Names exceeding this limit overflow the fixed-size stack buffer, corrupting adjacent stack memory and potentially overwriting return addresses or function pointers. CAN interfaces are critical for vehicle communication protocols in charging systems, and this initialization occurs early in the execution flow before privilege verification, expanding the attack surface.
RemediationAI
Upgrade EVerest everest-core to version 2026.02.0 or later, which contains the vendor-released patch addressing the buffer overflow (see GitHub Security Advisory GHSA-p47c-2jpr-mpwx at https://github.com/EVerest/EVerest/security/advisories/GHSA-p47c-2jpr-mpwx). Until patching is completed, implement strict validation of CAN interface names in configuration files and startup scripts, enforcing a maximum length of 15 characters (IFNAMSIZ-1) to prevent overflow conditions. Restrict local access to charging station systems and configuration management interfaces to trusted administrators only, and audit all existing CAN interface name configurations for compliance with length limits. Deploy file integrity monitoring on configuration files to detect unauthorized modifications that could introduce malicious interface names.
EVerest is an EV charging software stack. Prior to version 2025.10.0, an integer overflow occurring in `SdpPacket::parse
EVerest is an EV charging software stack. Prior to version 2025.10.0, during the deserialization of a `DC_ChargeLoopRes`
EVerest is an EV charging software stack. Prior to version 2025.10.0, once the module receives a SDP request, it creates
EVerest is an EV charging software stack. In versions 2025.9.0 and below, an attacker can exhaust the operating system's
EVerest is an EV charging software stack. Prior to version 2025.10.0, C++ exceptions are not properly handled for and by
Remote code execution vulnerability in EVerest electric vehicle charging software stack allows adjacent network attacker
EVerest is an EV charging software stack. Prior to version 2025.12.0, `is_message_crc_correct` in the DZG_GSH01 powermet
Stack-based buffer overflow in EVerest EV charging software stack enables local code execution when processing certifica
Concurrent access to shared memory in EVerest EV charging software (versions prior to 2026.02.0) enables remote attacker
Everest EV charging software prior to version 2025.9.0 contains an improper pointer arithmetic flaw in error handling wh
Out-of-bounds vector access in EVerest EV charging software (everest-core versions before 2026.02.0) enables remote unau
EVerest is an EV charging software stack. Prior to version 2025.10.0, the use of the `assert` function to handle errors
Same weakness CWE-121 – Stack-based Buffer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today