Severity by source
AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
4DescriptionGitHub Advisory
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to use-after-free. This is triggered by EV plug-in/unplug and RFID/RemoteStart/OCPP authorization events (or delayed authorization response). Version 2026.2.0 contains a patch.
AnalysisAI
EVerest charging software stack versions prior to 2026.02.0 contain a data race condition leading to use-after-free memory corruption, triggered by EV plug-in/unplug events and authorization flows (RFID, RemoteStart, OCPP). Unauthenticated physical attackers with high complexity can exploit this to leak sensitive information or cause denial of service on affected charging infrastructure. No public exploit identified at time of analysis.
Technical ContextAI
EVerest-core (cpe:2.3:a:everest:everest-core:*:*:*:*:*:*:*:*) is an open-source EV charging software stack handling real-time authorization events and plug state management. The vulnerability is rooted in CWE-416 (use-after-free), a memory safety issue where freed memory is referenced after deallocation. The data race occurs during concurrent processing of EV plug-in/unplug events alongside authorization response handlers (RFID card reads, RemoteStart API calls, or OCPP authorization confirmations). Without proper synchronization primitives or state validation, rapid sequences of these events can cause one thread to deallocate a data structure while another thread still holds a reference, leading to memory corruption.
RemediationAI
Upgrade EVerest-core to version 2026.02.0 or later, which contains the patch addressing the data race condition (see vendor advisory at https://github.com/EVerest/EVerest/security/advisories/GHSA-vgmh-mmg3-22m6). Until patching is completed, restrict physical access to charging stations in high-risk environments, implement sequential rather than concurrent authorization event processing if feasible via configuration, and monitor charging station logs and system health metrics for unexpected crashes or memory errors that may indicate exploitation attempts.
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
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
Same weakness CWE-416 – Use After Free
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-16220