EVerest's ISO15118 update_energy_transfer_modes overflow can corrupt EVSE state
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA everest-core (EVerest) Fixed in 2026.02.0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-27816
References
More EVerest vulnerabilities
- TI-2026-25456 EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio CVSS 3.1HIGH 8.2
- TI-2024-24822 EVerest has an integer overflow in the "v2g_incoming_v2gtp" function CVSS 3.1CRITICAL 9.1
- TI-2026-18308 EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload CVSS 3.1HIGH 8.8
- TI-2026-19334 EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ CVSS 3.1HIGH 8.4
- TI-2026-18154 EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing CVSS 3.1HIGH 8.4
- TI-2025-41718 EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop CVSS 3.1HIGH 8.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences