CVE-2026-33009

EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio

MEDIUM
6.5
CVSS Score
Published: March 26, 2026 at 04:39 PM UTC
Updated: June 17, 2026 at 10:36 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
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
PoC

Description

EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to C++ UB (potential memory corruption). This is triggered by an MQTT `everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging` message and results in `Charger::shared_context` / `internal_context` accessed concurrently without lock. 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_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/EVerest/EVerest/security/advisories/GHSA-33qh-fg6f-jjx5

SSVC — Action Prioritization

SSVCPoCAutomatablePartial impact

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

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
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