EvseV2G has sequence state validation bypass
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-287.
Summary
EVerest is an EV charging software stack. In versions up to and including 2025.12.1, it is possible to bypass the sequence state verification including authentication, and send requests that transition to forbidden states relative to the current one, thereby updating the current context with illegitimate data.cThanks to the modular design of EVerest, authorization is handled in a separate module and EVSEManager Charger internal state machine cannot transition out of the `WaitingForAuthentication` state through ISO 15118-2 communication. From this state, it was however possible through ISO 15118-2 messages which are published to the MQTT server to trick it into preparing to charge, and even to prepare to send current. The final requirement to actually send current to the EV was the closure of the contactors, which does not appear to be possible without leaving the `WaitingForAuthentication` state and leveraging ISO 15118-2 messages. As of time of publication, no fixed versions are available.
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
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-24003
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