Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPlace crafted certificate file with 100-char filename
-
DeliveryTrigger off-by-one check in IsoMux parser
-
ExploitOverflow file_names array on stack
-
ExecutionCorrupt stack canary and return pointer
-
ImpactExecute arbitrary code in EVerest process
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Off-by-one prevention
|
| Exploitation Conditions | Local attacker must place a crafted certificate file with exactly 100-character filename in EVerest's certificate directory on affected systems running versions prior to 2026.02.0. No authentication or user interaction required. Stack-based buffer overflow enables code execution with local privileges. |
| Impact | The CVSS base score of 8.4 reflects high severity, with the vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H indicating local attack vector, low complexity, no privileges required, and high impact across confidentiality, integrity, and availability. The local attack vector (AV:L) significantly constrains real-world exploitability compared to network-accessible vulnerabilities, requiring the attacker to have local filesystem access to the certificate directory. The PR:N designation means no authentication is required once local access is obtained. No public exploit identified at time of analysis, and no EPSS or KEV status data provided suggests this is not yet observed in active exploitation campaigns. However, the low attack complexity (AC:L) and availability of detailed technical information in the GitHub security advisory increase the likelihood of future exploit development. For EV charging infrastructure deployed in physically secured environments with restricted local access, the practical risk is moderate despite the high CVSS score. For installations where local access controls are weak or where the charging software runs on multi-tenant systems, this represents a critical risk requiring immediate patching. |
| Exploit ScenarioDerived | An attacker with local filesystem access to the EV charging system places a specially crafted certificate file with a filename of exactly 100 characters in the certificate directory monitored by the IsoMux component. When EVerest processes this certificate during initialization or certificate refresh operations, the off-by-one check fails to reject the oversized filename, triggering a stack buffer overflow that overwrites return addresses or function pointers with attacker-controlled data, enabling arbitrary code execution with the privileges of the EVerest process. Given the local attack vector (AV:L) and low complexity (AC:L), exploitation is straightforward once filesystem access is achieved. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
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.
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.
Affected VersionsENISA
Affected Packages
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 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.
Know when Everest 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
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
3DescriptionGitHub 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.
Executive ViewAI
EVerest-core versions prior to 2026.02.0 contain a stack buffer overflow in the IsoMux component that allows local attackers to execute arbitrary code without authentication when processing specially crafted certificate filenames. This vulnerability directly threatens the integrity and availability of EV charging infrastructure, potentially enabling attackers with local access to compromise charging stations and disrupt service delivery.
Apply vendor patch to EVerest-core version 2026.02.0 or later. If immediate patching is not feasible, restrict local physical access to affected charging station hardware and monitor for anomalous file processing activities targeting certificate pathways; however, patching is the primary remediation.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Related Vulnerabilities in EVerest Buffer Overflow and Data Race
View all 6EVerest 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
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
EUVD-2026-16173
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB