CVE-2026-26070: everest-core · Race Condition
Affects everest-coreSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium : upgrade to 2026.02.0 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.02.0
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade everest-core and everest/everest-core to 2026.02.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EVeresteverest-core | Affected
| Fixed in
|
GitHubeverest/everest-corepkg:github/everest/everest-coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade to EVerest everest-core version 2026.02.0 or later, which contains the official patch fixing the race condition by implementing proper synchronization mechanisms. 2. If immediate upgrade is not feasible, implement strict access controls to limit local or network access to the charging software environment, reducing the risk of triggering the race condition. 3. Monitor EV charging system logs and stability metrics for signs of crashes or unexpected restarts that may indicate exploitation attempts. 4. Conduct code audits and concurrency testing on custom or integrated components interacting with the everest-core to identify and remediate similar synchronization issues. 5. Employ runtime protections such as memory corruption detection tools or containerization to isolate the charging software and minimize impact of potential crashes. 6. Coordinate with EV infrastructure vendors and operators to ensure timely patch deployment and incident response readiness. 7. Educate operational staff on the importance of applying updates and monitoring for anomalies related to charging session disruptions.
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 an EV SoC update with powermeter periodic update and unplugging/SessionFinished state. Version 2026.2.0 contains a patch.