Skip to main content
VulnerabilityPublished

CVE-2026-26074: everest-core · Race Condition

Affects everest-coreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.0 High : upgrade to 2026.02.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.02.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade everest-core and everest/everest-core to 2026.02.0.

Affected software

ProductAffectedFixed in
EVeresteverest-coreAffected
  • <2026.02.0
Fixed in
  • 2026.02.0
GitHubeverest/everest-corepkg:github/everest/everest-coreOther threatsAffected
  • <2026.02.0
Fixed in
  • 2026.02.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade everest-core to version 2026.02.0 or later, which contains the official patch fixing the race condition. Until patching is possible, implement network-level controls to restrict or monitor CSMS GetLog and UpdateFirmware requests, especially from untrusted sources, to reduce the likelihood of triggering the race condition. Employ runtime monitoring tools capable of detecting data races or abnormal event_queue behavior. Conduct thorough testing of EVSE fault event handling under concurrent conditions to identify and mitigate synchronization issues. Engage with the vendor for any additional recommended configuration changes or hotfixes. Incorporate robust concurrency testing and static analysis in the development lifecycle to prevent similar issues. Finally, maintain incident response readiness to quickly address any service disruptions related to this vulnerability.

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.

References

Community reviews

Loading reviews…