EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA everest-core (EVerest) Fixed in 2026.02.0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-33009
References
More EVerest vulnerabilities
- TI-2024-24822 EVerest has an integer overflow in the "v2g_incoming_v2gtp" function CVSS 3.1CRITICAL 9.1
- TI-2026-18308 EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload CVSS 3.1HIGH 8.8
- TI-2026-19334 EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ CVSS 3.1HIGH 8.4
- TI-2026-18154 EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing CVSS 3.1HIGH 8.4
- TI-2025-41718 EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop CVSS 3.1HIGH 8.4
- TI-2025-41717 Resource allocation without limits in everest-core CVSS 3.1HIGH 7.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences