Skip to main content

Everest EUVDEUVD-2026-16218

| CVE-2026-26074 HIGH
Race Condition (CWE-362)
2026-03-26 GitHub_M
7.0
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send CSMS GetLog/UpdateFirmware request
  2. Delivery
    Trigger concurrent EVSE fault event
  3. Exploit
    Race condition accesses event_queue
  4. Execution
    Corrupt std::map data structure
  5. Impact
    Denial of service or information disclosure

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

EVerest versions prior to 2026.02.0. Attacker must simultaneously send CSMS GetLog or UpdateFirmware network request while EVSE experiences a physical fault event. AC:H indicates race condition timing difficulty. No authentication required; no user interaction needed.

Impact

Real-world risk is moderate despite the 7.0 CVSS score. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H) indicates network-accessible attack surface but high complexity (AC:H) requiring precise timing to trigger the race condition between network requests and physical hardware events. SSVC framework corroborates lower urgency: exploitation status is none, the vulnerability is not automatable (requires specific environmental conditions with concurrent CSMS commands and EVSE faults), and technical impact is partial. The unauthenticated attack vector (PR:N) is concerning for internet-exposed charging infrastructure, but the AC:H requirement significantly reduces likelihood of successful exploitation. No public exploit identified at time of analysis. The primary risk is to availability (A:H) in production EV charging networks where service disruption has safety and operational consequences, while confidentiality and integrity impacts remain limited (C:L/I:L). Organizations with air-gapped or network-segmented charging infrastructure face lower practical risk.

Exploit ScenarioDerived

A remote attacker sends carefully timed CSMS GetLog or UpdateFirmware requests to an internet-exposed EV charging station while monitoring for or triggering EVSE fault conditions (e.g., through electrical manipulation or environmental stress during active charging sessions). The simultaneous processing of the network command and physical fault event triggers the race condition, corrupting the internal event queue. Successful exploitation could leak sensitive operational logs containing user charging session data, corrupt firmware update state leading to failed security patches, or crash the charging station controller causing denial of service during critical charging operations. The high attack complexity (AC:H) requires precise timing and knowledge of station operational state, but no authentication is required (PR:N) for CSMS protocol access on misconfigured deployments.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 26, 2026

Concurrent access to an internal event queue in EVerest-core (EV charging software stack) enables remote attackers to corrupt critical data structures when CSMS GetLog or UpdateFirmware requests coincide with EVSE fault events, potentially causing information disclosure, data integrity issues, and high availability impact. The vulnerability affects all versions prior to 2026.02.0, for which a vendor patch is available. SSVC analysis indicates no current exploitation, non-automatable attack surface, and partial technical impact. EPSS data not provided; no public exploit identified at time of analysis.

RemediationAI

Upgrade EVerest everest-core to version 2026.02.0 or later, which contains a vendor-released patch addressing the data race condition (see GitHub advisory GHSA-p3hg-vqgv-h524 at https://github.com/EVerest/EVerest/security/advisories/GHSA-p3hg-vqgv-h524). Until patching is possible, implement network segmentation to restrict CSMS protocol access to trusted management networks only, reducing exposure to unauthenticated remote attackers. Monitor charging stations for anomalous behavior including unexpected restarts or log corruption following GetLog or UpdateFirmware operations coinciding with hardware fault events. Consider rate-limiting CSMS administrative commands during peak operational periods when EVSE faults are more probable. For critical infrastructure deployments, test the patch in non-production environments first to validate compatibility with existing CSMS integrations.

Affected VersionsENISA

everest-core < 2026.02.0

Affected Packages

euvd everest_core fix: 2026.02.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

EVerest-core (cpe:2.3:a:everest:everest-core) is an open-source software stack for electric vehicle charging infrastructure, managing communication between charging stations and central management systems (CSMS). The vulnerability is a classic race condition (CWE-362) where simultaneous network-triggered administrative commands (GetLog, UpdateFirmware via CSMS protocol) and physical hardware events (EVSE faults) cause unsynchronized access to a shared std::map containing std::queue objects. Thread Sanitizer (TSAN) tooling detected the concurrent writes to the event_queue data structure. Without proper mutex protection or atomic operations, this data race can corrupt the C++ Standard Template Library containers, leading to unpredictable behavior including memory corruption, leaked sensitive log data, or denial of service when the queue state becomes inconsistent.

Know when Everest gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.0 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

Lifecycle Timeline

3
Analysis Updated
Apr 16, 2026 - 06:13 EUVD-patch-fix
executive summary
Patch available
Apr 16, 2026 - 05:29 EUVD
2026.02.0
CVE Published
Mar 26, 2026 - 16:19 nvd
HIGH 7.0

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

CVE-2026-26074 affects EVerest-core EV charging software, allowing remote attackers to corrupt critical data structures and cause information disclosure or service disruption when specific charging management requests coincide with system faults. Organizations operating EV charging infrastructure using vulnerable EVerest versions risk data integrity compromise and availability disruption, requiring immediate assessment of deployed versions and patch planning.

Business Impact: High
Compensating Controls

Apply vendor patch: EVerest-core version 2026.02.0 or later. If immediate patching unavailable, implement network segmentation to restrict CSMS and EVSE communication to trusted networks only; monitor event queue and firmware update logs for concurrent anomalous requests; consider temporary suspension of remote firmware update operations until patch is deployed.

Threat Intelligence Overview

EPSS Score
0.0%
Top 90% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy