EVerest has race-condition-induced std::map corruption in OCPP 1.6 evse_soc_map

published 2026-03-26 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-16207

cvss: 4.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

linuxfoundation everest 2026.02.0
linuxfoundation libocpp 2026.02.0

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 7 mo ago (2026-03-26)

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.2	CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

EVerest everest-core

Classification

Weakness

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

github.com /EVerest/EVerest/security/advisories/GHSA-9xwc-49c4-p79v
vendor-advisory

Sources

CVE List CVE-2026-26072
NVD CVE-2026-26072

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary