CVE-2026-24003: EvseV2G has sequence state validation bypass
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-24003?
CVE-2026-24003 has a high severity due to the potential for unauthorized access and state transitions in EV charging operations.
How do I fix CVE-2026-24003?
To fix CVE-2026-24003, update to a version of EVerest later than 2025.12.1 that includes the necessary security patches.
What software is affected by CVE-2026-24003?
CVE-2026-24003 affects versions of the EVerest software stack up to and including version 2025.12.1.
What does CVE-2026-24003 exploit?
CVE-2026-24003 exploits a bypass in sequence state validation, allowing unauthorized requests to forbidden states.
Is CVE-2026-24003 easy to exploit?
Yes, CVE-2026-24003 can be exploited without proper authentication checks, making it easier for attackers to transition states.