Skip to main content

Everest CVE-2026-33015

| EUVDEUVD-2026-16254 MEDIUM
Incorrect Authorization (CWE-863)
2026-03-26 GitHub_M
5.2
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
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.

Impact

The risk profile is moderate in real-world environments but severity is amplified by intent. CVSS 5.2 (Medium) reflects the combination of physical attack vector (AV:P), low complexity (AC:L), no privileges required (PR:N), and integrity impact (I:H) with availability degradation (A:L). The SSVC framework shows exploitation is feasible (POC available), non-automatable (requires physical access and BCB manipulation), and has partial technical impact (session restart, billing bypass). The lack of CISA KEV confirmation means no confirmed active exploitation in the wild, reducing urgency relative to the CVSS score. However, the attack is not complex once physical proximity is achieved, and the impact-bypassing CSMS stop commands and billing controls-represents a significant operational and financial risk in commercial charging networks. Organizations with high-traffic public charging infrastructure should prioritize patching; isolated or monitored installations face lower risk.

Exploit ScenarioDerived

An EV operator at a public charging station, after being issued a RemoteStop by the CSMS (e.g., due to payment failure or session timeout), physically toggles the vehicle's Battery Control Box to reset the EVSE. Because the EVSE does not validate this toggle against the prior CSMS stop command, it transitions back to PrepareCharging and resumes charging without CSMS authorization. The operator's session billing is bypassed and the charging session continues indefinitely or until manual intervention occurs. A proof-of-concept for this state-machine bypass has been published, though exploitation requires physical access to the vehicle and charging connector during the charging session.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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

EVerest charging software stack versions prior to 2026.02.0 allow EV operators to bypass remote stop commands issued by a Charging Station Management System (CSMS) by toggling the EV's Battery Control Box (BCB), causing the EVSE to return to PrepareCharging state and restart charging sessions. This circumvents billing, operational, and safety controls enforced by remote stop functionality. A proof-of-concept exists and the vulnerability has been patched in version 2026.02.0, though the attack requires physical proximity to the charging equipment (CVSS attack vector: Physical).

RemediationAI

Upgrade EVerest-core to version 2026.02.0 or later immediately. This version contains the vendor-released patch that restores the irreversibility of RemoteStop by properly validating BCB toggle inputs against CSMS stop state. Until patching is feasible in production environments, implement physical security controls around charging equipment to prevent unauthorized BCB manipulation, enforce strict monitoring of CSMS RemoteStop commands and verify that charging sessions actually terminate, and consider disabling BCB-driven state transitions at the firmware level if the charging equipment supports such configuration. Review the GitHub Security Advisory (https://github.com/EVerest/EVerest/security/advisories/GHSA-pw9q-2287-cchc) for detailed deployment guidance and any interim configuration flags.

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-core (cpe:2.3:a:everest:everest-core:*:*:*:*:*:*:*:*) is an open-source EV charging software stack that manages the state machine governing EVSE (Electric Vehicle Supply Equipment) charging sessions, including transitions between states such as PrepareCharging and Active charging. The vulnerability stems from insufficient validation of state transition guards after a RemoteStop command from the CSMS triggers a StopTransaction. CWE-863 (Incorrect Authorization) indicates that the EVSE does not properly enforce authorization logic to prevent unauthorized state transitions-specifically, the BCB toggle input is not validated against the previous remote stop command, allowing the EV to force a return to PrepareCharging. The CSMS remote stop mechanism is designed to be irreversible and enforce billing/safety boundaries; this flaw breaks that guarantee by allowing the EV itself to override the CSMS decision through a low-level signal.

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

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 5.2 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

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

CVSS VectorGitHub Advisory

Attack Vector
Physical
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
2026.02.0
CVE Published
Mar 26, 2026 - 16:42 nvd
MEDIUM 5.2

DescriptionGitHub Advisory

EVerest is an EV charging software stack. Prior to version 2026.02.0, even immediately after CSMS performs a RemoteStop (StopTransaction), the EVSE can return to PrepareCharging via the EV's BCB toggle, allowing session restart. This breaks the irreversibility of remote stop and can bypass operational/billing/safety controls. Version 2026.02.0 contains a patch.

Executive ViewAI

Why It Matters

Organizations using EVerest should be aware of moderate risk from CVE-2026-33015, a incorrect authorization vulnerability rated CVSS 5.2. Attackers could gain access beyond their authorized level. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.0%
Top 96% exploitable
Data Quality
7 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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
Defer
Exploitation
Poc
System Exposure· derived
Small
Automatable
No
Human Impact
Low
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2025-68137 HIGH POC
8.3 Jan 21

EVerest is an EV charging software stack. Prior to version 2025.10.0, an integer overflow occurring in `SdpPacket::parse

CVE-2025-68141 HIGH POC
7.4 Jan 21

EVerest is an EV charging software stack. Prior to version 2025.10.0, during the deserialization of a `DC_ChargeLoopRes`

CVE-2025-68136 HIGH POC
7.4 Jan 21

EVerest is an EV charging software stack. Prior to version 2025.10.0, once the module receives a SDP request, it creates

CVE-2025-68133 HIGH POC
7.4 Jan 21

EVerest is an EV charging software stack. In versions 2025.9.0 and below, an attacker can exhaust the operating system's

CVE-2025-68135 MEDIUM POC
6.5 Jan 21

EVerest is an EV charging software stack. Prior to version 2025.10.0, C++ exceptions are not properly handled for and by

CVE-2025-68132 MEDIUM POC
4.6 Jan 21

EVerest is an EV charging software stack. Prior to version 2025.12.0, `is_message_crc_correct` in the DZG_GSH01 powermet

CVE-2026-23995 HIGH
8.4 Mar 26

Stack-based buffer overflow in EVerest EV charging software allows unauthenticated local attackers to execute arbitrary

CVE-2026-22593 HIGH
8.4 Mar 26

Stack-based buffer overflow in EVerest EV charging software stack enables local code execution when processing certifica

CVE-2026-33009 HIGH
8.2 Mar 26

Concurrent access to shared memory in EVerest EV charging software (versions prior to 2026.02.0) enables remote attacker

CVE-2026-23955 MEDIUM POC
4.2 Jan 21

Everest EV charging software prior to version 2025.9.0 contains an improper pointer arithmetic flaw in error handling wh

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy