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.
References
| Link | Resource |
|---|---|
| https://github.com/EVerest/everest-core/blob/main/modules/EVSE/EvseV2G/iso_server.cpp#L44 | Product |
| https://github.com/EVerest/everest-core/security/advisories/GHSA-9vv5-67cv-9crq | Mitigation Vendor Advisory |
Configurations
History
17 Feb 2026, 20:48
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:o:linuxfoundation:everest:*:*:*:*:*:*:*:* | |
| References | () https://github.com/EVerest/everest-core/blob/main/modules/EVSE/EvseV2G/iso_server.cpp#L44 - Product | |
| References | () https://github.com/EVerest/everest-core/security/advisories/GHSA-9vv5-67cv-9crq - Mitigation, Vendor Advisory | |
| First Time |
Linuxfoundation
Linuxfoundation everest |
26 Jan 2026, 22:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-01-26 22:15
Updated : 2026-02-17 20:48
NVD link : CVE-2026-24003
Mitre link : CVE-2026-24003
CVE.ORG link : CVE-2026-24003
JSON object : View
Products Affected
linuxfoundation
- everest