CVE-2026-24003
Unknown Unknown - Not Provided
Authentication Bypass in EVerest EVSEManager via ISO 15118-2 Messages

Publication date: 2026-01-26

Last updated on: 2026-02-17

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-26
Last Modified
2026-02-17
Generated
2026-05-07
AI Q&A
2026-01-27
EPSS Evaluated
2026-05-05
NVD
CVE-2026-24003
EUVD
EUVD-2026-4652
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linuxfoundation everest to 2025.12.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-287 When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the EVerest EV charging software stack allows an attacker to bypass sequence state verification and authentication. By sending ISO 15118-2 messages published to the MQTT server, an attacker can trick the internal state machine of the EVSEManager Charger into transitioning to forbidden states, such as preparing to charge or preparing to send current, even while still in the 'WaitingForAuthentication' state. However, the final step of actually sending current requires leaving this state, which is not possible through this vulnerability.


How can this vulnerability impact me? :

The vulnerability can allow unauthorized manipulation of the EV charging process by bypassing authentication and state verification. This could lead to the system preparing to charge or send current illegitimately, potentially causing operational disruptions or misuse of the charging infrastructure. However, the attacker cannot actually send current without proper state transitions, limiting the impact to preparation stages.


What immediate steps should I take to mitigate this vulnerability?

As of the time of publication, no fixed versions are available. Immediate mitigation steps are not specified in the provided information.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart