EUVD-2026-16173Severity 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, an off-by-one check in IsoMux certificate filename handling causes a stack-based buffer overflow when a filename length equals MAX_FILE_NAME_LENGTH (100). A crafted filename in the certificate directory can overflow file_names[idx], corrupting stack state and enabling potential code execution. Version 2026.02.0 contains a patch.
AnalysisAI
Stack-based buffer overflow in EVerest EV charging software stack enables local code execution when processing certificate filenames of exactly 100 characters due to off-by-one boundary check error in IsoMux component. EVerest-core versions prior to 2026.02.0 are affected (CPE cpe:2.3:a:everest:everest-core). The vulnerability has a CVSS score of 8.4 with local attack vector and no privilege requirements (AV:L/PR:N), allowing unauthenticated local attackers to achieve code execution. No public exploit identified at time of analysis, though technical details are available in GitHub security advisory GHSA-cpqf-mcqc-783m.
Technical ContextAI
The vulnerability affects the everest-core component of EVerest (cpe:2.3:a:everest:everest-core), an open-source software stack for electric vehicle charging infrastructure. The root cause is CWE-193 (Off-by-one Error) in the IsoMux certificate filename handling logic. The code performs an incorrect boundary check using equality (==) instead of strict less-than (<) when validating filenames against MAX_FILE_NAME_LENGTH (100 bytes). When a certificate filename length equals exactly 100 characters, the off-by-one condition passes validation but causes a write beyond the allocated buffer boundary for file_names[idx], corrupting adjacent stack memory. This stack-based buffer overflow enables control of return addresses, function pointers, or other critical stack data structures, potentially leading to arbitrary code execution in the context of the EV charging software.
RemediationAI
Upgrade EVerest everest-core to version 2026.02.0 or later, which contains a patch addressing the off-by-one boundary check error (vendor-released patch: version 2026.02.0). Refer to the GitHub security advisory at https://github.com/EVerest/EVerest/security/advisories/GHSA-cpqf-mcqc-783m for patch details and release notes. Until patching is feasible, implement defense-in-depth controls including restricting filesystem access to the certificate directory through operating system permissions (chmod/chown), monitoring certificate filenames for suspicious length patterns at or near 100 characters, and deploying the EV charging software in isolated environments with strong local access controls. Consider filesystem integrity monitoring to detect unauthorized certificate file placement. Additional advisory information is available at VulDB https://vuldb.com/?id.353634.
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 allows unauthenticated local attackers to execute arbitrary
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-193 – Off-by-one Error
View allShare
External POC / Exploit Code
Leaving vuln.today