Vulnerability in Everest Everest-Core

CVE-2026-26072

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.

Vulnerability class: Race Condition

Published · last modified .

CVSS v3 metric

CVSS v3 base score 4.2 (Medium). Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.

EPSS exploit prediction

EPSS: 0.001 (2.6th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 3rd percentile — 2.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-26072: held from 0.001 to 0.001.

EPSS over last 30 days · oldest: 0.001 · newest: 0.001 · change: 0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-26072?
CVE-2026-26072 is a medium-severity vulnerability in Everest Everest-Core, classified under Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition). CVSS score: 4.2/10. Published 2026-03-26.
How severe is CVE-2026-26072?
Medium severity. CVSS v3 base score is 4.2 out of 10.