Medium severity · published Mar 26, 2026
CVE-2026-26072
EVerest has race-condition-induced std::map corruption in OCPP 1.6 evse_soc_map
4.2
CVSS
0.1%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack vector
Physical
Complexity
High
Privileges
None
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 3% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EV
everest-core · EVerest
< 2026.02.0 · source: vendor
EV
Everest · Linuxfoundation
before 2026.02.0 · source: NVD
Affected product
EV
everest-core
EVerest
More from everest-core
9.1
CVE-2026-27816
EVerest's ISO15118 update_energy_transfer_modes overflow can corrupt EVSE state
9.1
CVE-2026-27815
EVerest: ISO15118 session_setup payment options overflow can corrupt EVSE state
8.8
CVE-2026-22790
EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload
7.8
CVE-2026-23995
EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ
7.8
CVE-2026-22593
EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing