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

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 CVE-2026-33009

Q: Which versions of Everest 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.

EUVD-2026-16250 HIGH

Race Condition (CWE-362)

2026-03-26 GitHub_M

Buffer Overflow Race Condition Everest Everest Core

8.2

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Send MQTT message to everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging
Delivery

Trigger concurrent access to Charger::shared_context without lock
Exploit

Cause data race condition
Execution

Memory corruption via C++ undefined behavior
Impact

Crash charging service or corrupt state

Vulnerability Assessment

Weakness	CWE CWE-362 OWASP Top 10:2025 A06:2025 - Insecure Design ASVS 5.0 V15 - Secure Coding and Architecture Concurrency control, locking MITRE ATT&CK 1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Remote unauthenticated attacker sending crafted MQTT message `everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging` to EVerest versions before 2026.02.0. Requires MQTT broker accessible to attacker and EVerest configured with MQTT external connector enabled.
Impact	The CVSS base score of 8.2 reflects a network-accessible attack requiring low complexity and no privileges or user interaction (AV:N/AC:L/PR:N/UI:N), with high availability impact and low integrity impact (C:N/I:L/A:H). This scoring indicates the primary risk is denial-of-service against EV charging infrastructure with secondary data integrity concerns. Real-world risk is moderated by several factors: the vulnerability requires specific MQTT message injection into EVerest deployments, race conditions are inherently probabilistic (requiring precise timing to exploit), and no public exploit identified at time of analysis. The confined deployment footprint of EVerest (specialized EV charging infrastructure rather than mass-market software) limits exposure compared to widely-deployed applications. However, the unauthenticated network attack vector and presence of a GitHub security advisory (GHSA-33qh-fg6f-jjx5) indicate this is a genuine architectural flaw warranting priority remediation in affected environments. The availability impact is particularly concerning for critical infrastructure applications where charging station disruption affects operational reliability.
Exploit ScenarioDerived	An attacker on the network sends crafted MQTT messages to the everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging topic while the charging station is actively managing vehicle sessions. By flooding multiple switch commands in rapid succession, the attacker increases probability of triggering the race condition where concurrent threads access Charger::shared_context without locking, potentially corrupting internal state and causing the charging controller to crash or behave unpredictably. The unauthenticated network access (CVSS PR:N) and low attack complexity mean exploitation requires only MQTT protocol knowledge and network connectivity to the charging infrastructure.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 26, 2026

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

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.

Affected VersionsENISA

everest-core < 2026.02.0

Affected Packages

euvd everest_core fix: 2026.02.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

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.

Know when Everest gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

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

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

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.02.0

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.

Executive ViewAI

Why It Matters

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 MQTT messages. Organizations operating EV charging infrastructure face potential service outages and data integrity compromise if unpatched systems are accessible to network attackers.

Business Impact: High

Compensating Controls

Apply vendor patch (version 2026.02.0 or later). If immediate patching cannot be completed: restrict MQTT broker access to authenticated clients only via firewall or network segmentation; disable remote MQTT connectivity and require VPN for all charger management; implement network monitoring to detect anomalous MQTT command patterns; establish incident response procedures for charging service disruption.

Threat Intelligence Overview

EPSS Score

0.0%

Top 89% exploitable

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

Vulnrichment

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision

Out-of-Cycle

Exploitation

Poc

System Exposure· derived

Open

Automatable

Yes

Human Impact

High

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +41

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Buffer Overflow HIGH

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Race Condition MEDIUM

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).