CVE-2026-33009 | EVerest everest-core 2025.9.0/2025.10.0/2025.12.0 switch_three_phases_while_charging race condition (GHSA-33qh-fg6f-jjx5 / EUVD-2026-16250)

VDB-353679 · CVE-2026-33009 · GHSA-33QH-FG6F-JJX5 EVEREST EVEREST-CORE 2025.9.0/2025.10.0/2025.12.0 SWITCH_THREE_PHASES_WHILE_CHARGING RACE CONDITION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.2 $0-$5k 1.99+ Summaryinfo A vulnerability marked as critical has been reported in EVerest everest-core. The impacted element is an unknown function of the file /everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging. Performing a manipulation results in race condition. This vulnerability is cataloged as CVE-2026-33009. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component. Detailsinfo A vulnerability was found in EVerest everest-core. It has been classified as critical. This affects an unknown code of the file /everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on integrity, and availability. The summary by CVE is: 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. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-33009 since 03/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. Upgrading to version 2026.02.0 eliminates this vulnerability. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-16250). Productinfo Vendor EVerest Name everest-core Version 2025.9.0 2025.10.0 2025.12.0 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 7.3 VulDB Meta Temp Score: 7.2 VulDB Base Score: 6.5 VulDB Temp Score: 6.2 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.2 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Race condition CWE: CWE-362 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: everest-core 2026.02.0 Timelineinfo 03/17/2026 CVE reserved 03/26/2026 +9 days Advisory disclosed 03/26/2026 +0 days VulDB entry created 03/26/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-33qh-fg6f-jjx5 Status: Confirmed CVE: CVE-2026-33009 (🔒) GCVE (CVE): GCVE-0-2026-33009 GCVE (VulDB): GCVE-100-353679 EUVD: 🔒 Entryinfo Created: 03/26/2026 19:00 Updated: 03/26/2026 19:38 Changes: 03/26/2026 19:00 (64), 03/26/2026 19:38 (1) Complete: 🔍 Cache ID: 99:DD8:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸