CVE-2026-26074 | EVerest everest-core 2025.9.0/2025.10.0/2025.12.0 std::map race condition (GHSA-p3hg-vqgv-h524)

VDB-353694 · CVE-2026-26074 · GHSA-P3HG-VQGV-H524 EVEREST EVEREST-CORE 2025.9.0/2025.10.0/2025.12.0 STD::MAP RACE CONDITION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.2 $0-$5k 2.89+ Summaryinfo A vulnerability described as problematic has been identified in EVerest everest-core. Affected by this vulnerability is the function std::map. The manipulation results in race condition. This vulnerability is cataloged as CVE-2026-26074. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is recommended. Detailsinfo A vulnerability, which was classified as problematic, was found in EVerest everest-core. Affected is the function std::map. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes: EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::map` 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. The advisory is available at github.com. This vulnerability is traded as CVE-2026-26074 since 02/10/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. Upgrading to version 2026.02.0 eliminates this vulnerability. Productinfo Vendor EVerest Name everest-core Version 2025.9.0 2025.10.0 2025.12.0 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.3 VulDB Meta Temp Score: 6.2 VulDB Base Score: 5.6 VulDB Temp Score: 5.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.0 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Race condition CWE: CWE-362 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: everest-core 2026.02.0 Timelineinfo 02/10/2026 CVE reserved 03/26/2026 +44 days Advisory disclosed 03/26/2026 +0 days VulDB entry created 03/26/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-p3hg-vqgv-h524 Status: Confirmed CVE: CVE-2026-26074 (🔒) GCVE (CVE): GCVE-0-2026-26074 GCVE (VulDB): GCVE-100-353694 Entryinfo Created: 03/26/2026 19:05 Changes: 03/26/2026 19:05 (64) Complete: 🔍 Cache ID: 99:1D9:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸