Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS v4.0 base score of 5.5 with vector AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N indicates local attack vector with low complexity, no privileges or user interaction required, resulting in high availability impact (service crash) but no direct confidentiality or integrity compromise of other security domains. SSVC analysis indicates no confirmed exploitation to date, non-automatable attack (requires crafted MQTT payload with specific charger state), and partial technical impact (denial of service via crash or EVSE state corruption). The local attack vector significantly reduces real-world risk compared to remote vulnerabilities, as it requires either local network access or MQTT broker compromise. Patch availability (version 2026.02.0) further mitigates urgency. However, the default-disabled schema validation and automotive critical infrastructure context warrant elevated attention for operators managing EV charging networks, particularly those with direct internet-exposed MQTT brokers or hostile internal network assumptions. |
| Exploit ScenarioDerived | An attacker with network access to an EVerest-Core MQTT broker (or who has compromised a legitimate MQTT client) crafts an oversized energy_transfer_modes list payload in an ISO15118 Cmd message containing more than 6 mode entries. When the charger processes this message with schema validation disabled, the handle_update_energy_transfer_modes function copies the entire list into the fixed 6-element array, overwriting adjacent EVSE state variables in memory. This causes either immediate process crash (denial of service to the charging station) or silent corruption of critical charging parameters, potentially affecting grid synchronization or vehicle charging safety. No public proof-of-concept exploit exists at this time, and successful exploitation requires either authenticated MQTT access or prior broker compromise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
EVerest-Core prior to version 2026.02.0 contains an out-of-bounds write vulnerability in the ISO15118_chargerImpl::handle_update_energy_transfer_modes function, where variable-length MQTT command payloads are copied into a fixed-size 6-element array without bounds checking. When schema validation is disabled by default, oversized payloads trigger memory corruption that can crash the EV charging service or corrupt adjacent EVSE (Electric Vehicle Supply Equipment) state, affecting the integrity and availability of EV charging infrastructure. No public exploit code has been identified at the time of analysis, but the vulnerability is patched in version 2026.02.0.
RemediationAI
Upgrade EVerest-Core to version 2026.02.0 or later, which contains the patch for the out-of-bounds write vulnerability. Until patching is completed, enable MQTT schema validation in the charger configuration to enforce payload size limits on Cmd messages sent to handle_update_energy_transfer_modes, and restrict MQTT broker access to trusted networks or authenticated clients only. Network segmentation of the MQTT broker from untrusted network segments is strongly recommended. Organizations managing EV charging infrastructure should consult the patch advisory at https://github.com/EVerest/EVerest/security/advisories/GHSA-gq54-j8f4-xj8c for deployment guidance specific to their architecture.
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
EVerest-Core (cpe:2.3:a:everest:everest-core) is an open-source EV charging software stack that implements ISO 15118 vehicle-to-grid communication protocols. The vulnerable code exists in the handle_update_energy_transfer_modes function within ISO15118_chargerImpl, which processes MQTT command payloads used for charging mode control. The root cause is CWE-787 (Out-of-bounds Write), a classic buffer overflow where a variable-length input list is copied into a statically-allocated array of exactly 6 elements without prior validation of input size. The default configuration disables schema validation on MQTT Cmd payloads, allowing oversized messages to reach the vulnerable code path unchecked. This is particularly critical in automotive charging contexts where EVSE state corruption could impact grid stability or vehicle safety systems.
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
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
EVerest is an EV charging software stack. Prior to versions to 2026.02.0, ISO15118_chargerImpl::handle_update_energy_transfer_modes copies a variable-length list into a fixed-size array of length 6 without bounds checking. With schema validation disabled by default, oversized MQTT Cmd payloads can trigger out-of-bounds writes and corrupt adjacent EVSE state or crash the process. Version 2026.02.0 contains a patch.
Executive ViewAI
Organizations using EVerest should be aware of moderate risk from CVE-2026-27816, a out-of-bounds write vulnerability rated CVSS 5.5. Exploitation could cause memory corruption or application crashes. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: enable ASLR/DEP, apply network segmentation.
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.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Related Vulnerabilities in EVerest Charging Software Memory Safety
View all 3EVerest 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
EUVD-2026-16226
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB