CVE-2026-26072 EVerest has race-condition-induced std::map corruption in OCPP 1.6 evse_soc_map
A race condition in EVerest EV charging software can corrupt memory during concurrent status updates, potentially causing crashes or undefined behavior.
- 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-26072?
CVE-2026-26072 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 EV SoC update with powermeter periodic update and unplugging/SessionFinished status. Version 2026.02.0 patches the issue.
Weakness: CWE-362
Which versions are affected by CVE-2026-26072?
It affects 1 product.
Products include Linuxfoundation Everest.
How do I fix CVE-2026-26072?
No fix has been published for CVE-2026-26072 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-26072 being exploited?
There is no known exploitation of CVE-2026-26072 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-9xwc-49c4-p79v.