A vulnerability categorized as critical has been discovered in EVerest everest-core 2025.9.0/2025.10.0/2025.12.0 . This issue affects the function ISO15118_chargerImpl::handle_update_energy_transfer_modes . The manipulation results in out-of-bounds write. This vulnerability is identified as CVE-2026-27816 . The attack is only possible with local access. There is not any exploit available. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353677 · CVE-2026-27816 · GHSA-GQ54-J8F4-XJ8C
EVEREST EVEREST-CORE 2025.9.0/2025.10.0/2025.12.0 HANDLE_UPDATE_ENERGY_TRANSFER_MODES OUT-OF-BOUNDS WRITE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.0 $0-$5k 1.81+
Summaryinfo
A vulnerability identified as critical has been detected in EVerest everest-core. Impacted is the function ISO15118_chargerImpl::handle_update_energy_transfer_modes. This manipulation causes out-of-bounds write. This vulnerability is tracked as CVE-2026-27816. The attack is restricted to local execution. No exploit exists. You should upgrade the affected component.
Detailsinfo
A vulnerability has been found in EVerest everest-core and classified as critical. Affected by this vulnerability is the function ISO15118_chargerImpl::handle_update_energy_transfer_modes. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-27816 since 02/24/2026. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
Upgrading to version 2026.02.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-16226).
Productinfo
Vendor
EVerest
Name
everest-core
Version
2025.9.0
2025.10.0
2025.12.0
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Out-of-bounds write
CWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: everest-core 2026.02.0
Timelineinfo
02/24/2026 CVE reserved
03/26/2026 +30 days Advisory disclosed
03/26/2026 +0 days VulDB entry created
03/26/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: GHSA-gq54-j8f4-xj8c
Status: Confirmed
CVE: CVE-2026-27816 (🔒)
GCVE (CVE): GCVE-0-2026-27816
GCVE (VulDB): GCVE-100-353677
EUVD: 🔒
Entryinfo
Created: 03/26/2026 19:00
Updated: 03/26/2026 19:38
Changes: 03/26/2026 19:00 (68), 03/26/2026 19:38 (1)
Complete: 🔍
Cache ID: 99:D29:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸