CVE-2026-26070 EVerest: OCPP 2.0.1 EV SoC Update Race Causes Charge Point Crash
A race condition in EVerest EV charging software causes charge point crashes during specific state transitions, requiring an upgrade to fix.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-26070?
CVE-2026-26070 is a medium-severity vulnerability in everest-core, published on 26 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to `std::map<std::optional>` concurrent access (container/optional corruption possible). The trigger is an EV SoC update with powermeter periodic update and unplugging/SessionFinished state. Version 2026.2.0 contains a patch.
Weakness: CWE-362
Which versions are affected by CVE-2026-26070?
It affects 1 product.
Products include Linuxfoundation Everest.
How do I fix CVE-2026-26070?
No fix has been published for CVE-2026-26070 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-26070 being exploited?
There is no known exploitation of CVE-2026-26070 in the wild and no public exploit code.
Other vulnerabilities in everest-core
- CVE-2026-22790 EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload
- CVE-2026-22593 EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing
- CVE-2026-23995 EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ
- CVE-2025-68137 EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop
- CVE-2026-33009 EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio
Sources
Also known as GHSA-498x-w527-jp3c.