CVE-2026-26074 EVerest: OCPP201 startup event_queue lock mismatch leads to std::map/std::queue data race
A data race in EVerest EV charging software can corrupt internal queues, potentially causing denial of service when specific network and physical events coincide.
- 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-26074?
CVE-2026-26074 is a high-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::map<std::queue>` corruption. The trigger is CSMS GetLog/UpdateFirmware request (network) with an EVSE fault event (physical). This results in TSAN reports concurrent access (data race) to `event_queue`. Version 2026.2.0 contains a patch.
Weakness: CWE-362
Which versions are affected by CVE-2026-26074?
It affects 1 product.
Products include Linuxfoundation Everest.
How do I fix CVE-2026-26074?
No fix has been published for CVE-2026-26074 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-26074 being exploited?
There is no known exploitation of CVE-2026-26074 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-p3hg-vqgv-h524.