CVE-2026-26073 EVerest: OCPP 1.6 heap corruption caused by lock-free insertion in event_queue
A data race in EVerest's event queue can cause memory corruption, potentially leading to code execution or denial of service in EV charging systems.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-26073?
CVE-2026-26073 is a medium-severity vulnerability in everest-core, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, 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 possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started). This results in a TSAN data race report and an ASAN/UBSAN misaligned address runtime error being observed. Version 2026.02.0 contains a patch.
Which versions are affected by CVE-2026-26073?
It affects 1 product.
Products include Linuxfoundation Everest.
How do I fix CVE-2026-26073?
No fix has been published for CVE-2026-26073 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-26073 being exploited?
There is no known exploitation of CVE-2026-26073 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-jf36-f4f9-7qc2.