Skip to main content

Everest CVE-2026-33014

| EUVDEUVD-2026-16252 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 CVSS 3.1 score of 5.2 (Medium) reflects a physically proximate attack vector (AV:P) with low complexity (AC:L), no special privileges required (PR:N), and no user interaction (UI:N). However, this is a scoped integrity impact (I:H) combined with availability loss (A:L), indicating partial system compromise rather than confidentiality breach. The SSVC framework assessment identifies exploitation as 'poc' (proof-of-concept available), non-automatable, with partial technical impact, suggesting this is an intermediate-priority vulnerability. The attack vector constraint (AV:P) significantly reduces real-world exploitation risk compared to network-adjacent or network attacks, as an attacker would need physical access to or control of the charging station network. The combination of a proven POC, lower EPSS exploitation probability (implied by medium CVSS and physical vector), and lack of active CISA KEV confirmation indicates this is a legitimate but not critical priority-organizations should patch in normal maintenance windows rather than emergency protocols.

Exploit ScenarioDerived

An attacker with local or network access to an EV charging station (satisfying the physical attack vector requirement) initiates a remote stop command while simultaneously delaying or manipulating the authorization response. The delayed authorization response reaches the system after the stop_transaction() precondition check, incorrectly restoring the authorized flag to true. As a result, the charging transaction remains active despite the PowerOff event, allowing continued power delivery to the vehicle or enabling billing manipulation. A proof-of-concept demonstrating this timing-based authorization bypass is publicly available, though successful exploitation requires precise control over network timing or direct access to the authorization service.

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-core prior to version 2026.02.0 fails to properly terminate EV charging transactions during remote stop operations due to a delayed authorization response that incorrectly restores the authorized flag to true, allowing transactions to remain open even after a PowerOff event triggers stop_transaction(). This authentication bypass affects EV charging infrastructure and enables continued power delivery after an operator-initiated remote stop command. A proof-of-concept exists but no public confirmation of active exploitation has been identified.

RemediationAI

Upgrade EVerest-core to version 2026.02.0 or later immediately using the official vendor release. Organizations should consult the GitHub Security Advisory (https://github.com/EVerest/EVerest/security/advisories/GHSA-43xm-5m3v-52hm) for deployment instructions and validation steps. Until patching can be completed, implement operational controls by restricting remote stop command execution to authenticated and authorized administrative users only, and conduct periodic transaction audits to verify that stopped sessions do not retain active charging state. Additionally, monitor charging infrastructure logs for anomalous authorization state transitions, particularly delayed responses to RemoteStop events that may indicate exploitation attempts.

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 software stack for EV charging infrastructure. The vulnerability stems from CWE-863 (Incorrect Authorization), specifically a timing or state-management flaw in the RemoteStop authorization handling logic. When a remote stop is initiated, the system should maintain a stopped state; however, a delayed authorization response during this window restores the 'authorized' state variable to true, which acts as a precondition gate for the stop_transaction() method. This creates a logic flaw where the authorization state contradicts the actual operational intent (stop), allowing the charging transaction to persist. The affected product is EVerest-core (CPE: cpe:2.3:a:everest:everest-core:*:*:*:*:*:*:*:*), which is widely used in EV charging station implementations.

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:40 nvd
MEDIUM 5.2

DescriptionGitHub Advisory

EVerest is an EV charging software stack. Prior to versions to 2026.02.0, during RemoteStop processing, a delayed authorization response restores authorized back to true, defeating the stop_transaction() call condition on PowerOff events. As a result, the transaction can remain open even after a remote stop. Version 2026.02.0 contains a patch.

Executive ViewAI

Why It Matters

Organizations using EVerest should be aware of moderate risk from CVE-2026-33014, 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