CVE-2026-26073

EVerest: OCPP 1.6 heap corruption caused by lock-free insertion in event_queue

MEDIUM
5.9
CVSS Score
Published: March 26, 2026 at 04:15 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
MEDIUM5.9
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started). This results in a TSAN data race report and an ASAN/UBSAN misaligned address runtime error being observed. Version 2026.02.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-jf36-f4f9-7qc2

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

5.9MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-122CWE-787

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