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.
Published: 2026-03-26
Score: 7 High
EPSS: < 1% Very Low
KEV: No
Impact: Data Corruption leading to Service Disruption
Action: Apply Patch
AI Analysis

Impact

A data race occurs in the startup event_queue of the EVerest EV charging software stack. The race between concurrent accesses to a std::map of std::queue structures can corrupt the internal data, potentially causing malfunctioning of the charging infrastructure or denial of service. The vulnerability may expose the system to inconsistent states that could be exploited for further attacks if contingent on corrupted data. The root cause is a synchronization flaw in the handling of event_queue.

Affected Systems

EVerest EV charging software stack, specifically the everest-core component. All releases prior to version 2026.02.0 are vulnerable. The affected code resides in the event handling module responsible for processing network requests from the CSMS and fault events from the EVSE.

Risk and Exploitability

The CVSS score is 7, indicating a high severity. The EPSS score of less than 1% suggests that exploitation is unlikely to be widespread, and the vulnerability is not listed in the CISA KEV catalog. The attack vector, inferred from the description, requires an attacker to send CSMS GetLog or UpdateFirmware requests while simultaneously an EVSE fault event occurs. This combination of a network request with a physical fault condition indicates that both a network-facing and a physical component must be engaged, which may reduce the breadth of potential attackers. However, the presence of a data race means that an attacker could precipitate service disruption if the conditions are met.

Generated by OpenCVE AI on March 31, 2026 at 05:45 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to version 2026.2.0 or later of everest-core.

Generated by OpenCVE AI on March 31, 2026 at 05:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 31 Mar 2026 03:00:00 +0000

Type Values Removed Values Added
First Time appeared Linuxfoundation
Linuxfoundation everest
CPEs cpe:2.3:o:linuxfoundation:everest:*:*:*:*:*:*:*:*
Vendors & Products Linuxfoundation
Linuxfoundation everest

Fri, 27 Mar 2026 08:45:00 +0000

Type Values Removed Values Added
First Time appeared Everest
Everest everest-core
Vendors & Products Everest
Everest everest-core

Thu, 26 Mar 2026 19:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 26 Mar 2026 16:45:00 +0000

Type Values Removed Values Added
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.
Title EVerest: OCPP201 startup event_queue lock mismatch leads to std::map/std::queue data race
Weaknesses CWE-362
References
Metrics cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H'}


Subscriptions

Everest Everest-core
Linuxfoundation Everest
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-03-26T18:24:25.673Z

Reserved: 2026-02-10T18:01:31.901Z

Link: CVE-2026-26074

cve-icon Vulnrichment

Updated: 2026-03-26T17:49:52.024Z

cve-icon NVD

Status : Analyzed

Published: 2026-03-26T17:16:33.407

Modified: 2026-03-30T20:57:44.247

Link: CVE-2026-26074

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-03-31T20:08:55Z

Weaknesses