What is the CVSS score of CVE-2026-33009?

CVE-2026-33009 has a CVSS 3.1 base score of 8.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H. EPSS exploitation probability: 0.0%.

Which versions of Everest Core are affected by CVE-2026-33009?

CVE-2026-33009 affects EVerest EV charging software versions prior to 2026.02.0, allowing unauthenticated remote attackers to corrupt shared memory and disrupt charging operations through malicious…. A patch is available.

How to fix or mitigate CVE-2026-33009?

Within 24 hours: Inventory all EVerest deployments and confirm current version numbers; isolate MQTT endpoints from untrusted networks if immediate patching is not feasible. Within 7 days: Apply vendor-released patch to upgrade all affected systems to version 2026.02.0 or later and validate patch installation. Within 30 days: Conduct post-patch validation testing on charging operations and implement network segmentation controls to restrict MQTT access to authorized systems only.

Everest Core CVE-2026-33009

EUVD-2026-16250 HIGH

Race Condition (CWE-362)

2026-03-26 GitHub_M

Race Condition Buffer Overflow Everest Core

8.2

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.2 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:13 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.02.0

EUVD ID Assigned

Mar 26, 2026 - 16:45 euvd

EUVD-2026-16250

Analysis Generated

Mar 26, 2026 - 16:45 vuln.today

CVE Published

Mar 26, 2026 - 16:39 nvd

HIGH 8.2

DescriptionGitHub Advisory

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.

AnalysisAI

Concurrent access to shared memory in EVerest EV charging software (versions prior to 2026.02.0) enables remote attackers to trigger undefined behavior and potential memory corruption through unauthenticated MQTT messages. The data race condition in Charger::shared_context occurs when processing switch_three_phases_while_charging commands without proper locking, yielding CVSS 8.2 (High) with potential for availability disruption and data integrity impact. No public exploit identified at time of analysis, though the attack vector is network-accessible without authentication requirements (CVSS:3.1/AV:N/AC:L/PR:N/UI:N).

Technical ContextAI

EVerest is an open-source electric vehicle charging station software stack deployed in EV infrastructure implementations. The vulnerability affects everest-core (CPE: cpe:2.3:a:everest:everest-core:*:*:*:*:*:*:*:*) and stems from CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization, commonly called a race condition). The flaw manifests when the MQTT message broker delivers everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging commands that trigger concurrent access to Charger::shared_context and internal_context data structures without mutex protection. This classic thread-safety violation in C++ creates undefined behavior where memory reads and writes may interleave unpredictably, potentially causing memory corruption, use-after-free conditions, or state inconsistencies in charging control logic.

RemediationAI

Upgrade EVerest everest-core to version 2026.02.0 or later, which contains the vendor-released patch addressing the concurrent access vulnerability (see https://github.com/EVerest/EVerest/security/advisories/GHSA-33qh-fg6f-jjx5). Until patching is feasible, implement network-level controls to restrict MQTT broker access to trusted administrative networks only, filtering the everest_external/nodered/*/cmd/switch_three_phases_while_charging message topic at the MQTT broker level if dynamic phase-switching is not operationally required. Deploy intrusion detection signatures monitoring for anomalous MQTT message patterns targeting EVerest command topics. Given the network-accessible attack vector without authentication requirements, prioritize patching for internet-facing or multi-tenant charging infrastructure deployments.