CVE-2026-26070

EVerest: OCPP 2.0.1 EV SoC Update Race Causes Charge Point Crash

MEDIUM
4.2
CVSS Score
Published: March 26, 2026 at 02:45 PM UTC
Updated: June 17, 2026 at 10:25 AM UTC
2 products affected across 2 vendorsEverestCore

Using everest-core by EVerest?

Get instant alerts when new vulnerabilities affect everest-core - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.2
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2026.02.0
Affected range stops below 2026.02.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMVendor Advisory
Source: cverecord
https://github.com/EVerest/EVerest/security/advisories/GHSA-498x-w527-jp3c

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
PHYSICAL
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card