Skip to main content

Everest CVE-2026-22593

| EUVDEUVD-2026-16173 HIGH
Off-by-one Error (CWE-193)
2026-03-26 GitHub_M
8.4
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

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

  1. Access
    Place crafted certificate file with 100-char filename
  2. Delivery
    Trigger off-by-one check in IsoMux parser
  3. Exploit
    Overflow file_names array on stack
  4. Execution
    Corrupt stack canary and return pointer
  5. Impact
    Execute arbitrary code in EVerest process

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Off-by-one prevention
Exploitation Conditions

Local attacker must place a crafted certificate file with exactly 100-character filename in EVerest's certificate directory on affected systems running versions prior to 2026.02.0. No authentication or user interaction required. Stack-based buffer overflow enables code execution with local privileges.

Impact

The CVSS base score of 8.4 reflects high severity, with the vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H indicating local attack vector, low complexity, no privileges required, and high impact across confidentiality, integrity, and availability. The local attack vector (AV:L) significantly constrains real-world exploitability compared to network-accessible vulnerabilities, requiring the attacker to have local filesystem access to the certificate directory. The PR:N designation means no authentication is required once local access is obtained. No public exploit identified at time of analysis, and no EPSS or KEV status data provided suggests this is not yet observed in active exploitation campaigns. However, the low attack complexity (AC:L) and availability of detailed technical information in the GitHub security advisory increase the likelihood of future exploit development. For EV charging infrastructure deployed in physically secured environments with restricted local access, the practical risk is moderate despite the high CVSS score. For installations where local access controls are weak or where the charging software runs on multi-tenant systems, this represents a critical risk requiring immediate patching.

Exploit ScenarioDerived

An attacker with local filesystem access to the EV charging system places a specially crafted certificate file with a filename of exactly 100 characters in the certificate directory monitored by the IsoMux component. When EVerest processes this certificate during initialization or certificate refresh operations, the off-by-one check fails to reject the oversized filename, triggering a stack buffer overflow that overwrites return addresses or function pointers with attacker-controlled data, enabling arbitrary code execution with the privileges of the EVerest process. Given the local attack vector (AV:L) and low complexity (AC:L), exploitation is straightforward once filesystem access is achieved.

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

Stack-based buffer overflow in EVerest EV charging software stack enables local code execution when processing certificate filenames of exactly 100 characters due to off-by-one boundary check error in IsoMux component. EVerest-core versions prior to 2026.02.0 are affected (CPE cpe:2.3:a:everest:everest-core). The vulnerability has a CVSS score of 8.4 with local attack vector and no privilege requirements (AV:L/PR:N), allowing unauthenticated local attackers to achieve code execution. No public exploit identified at time of analysis, though technical details are available in GitHub security advisory GHSA-cpqf-mcqc-783m.

RemediationAI

Upgrade EVerest everest-core to version 2026.02.0 or later, which contains a patch addressing the off-by-one boundary check error (vendor-released patch: version 2026.02.0). Refer to the GitHub security advisory at https://github.com/EVerest/EVerest/security/advisories/GHSA-cpqf-mcqc-783m for patch details and release notes. Until patching is feasible, implement defense-in-depth controls including restricting filesystem access to the certificate directory through operating system permissions (chmod/chown), monitoring certificate filenames for suspicious length patterns at or near 100 characters, and deploying the EV charging software in isolated environments with strong local access controls. Consider filesystem integrity monitoring to detect unauthorized certificate file placement. Additional advisory information is available at VulDB https://vuldb.com/?id.353634.

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

The vulnerability affects the everest-core component of EVerest (cpe:2.3:a:everest:everest-core), an open-source software stack for electric vehicle charging infrastructure. The root cause is CWE-193 (Off-by-one Error) in the IsoMux certificate filename handling logic. The code performs an incorrect boundary check using equality (==) instead of strict less-than (<) when validating filenames against MAX_FILE_NAME_LENGTH (100 bytes). When a certificate filename length equals exactly 100 characters, the off-by-one condition passes validation but causes a write beyond the allocated buffer boundary for file_names[idx], corrupting adjacent stack memory. This stack-based buffer overflow enables control of return addresses, function pointers, or other critical stack data structures, potentially leading to arbitrary code execution in the context of the EV charging software.

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 8.4 HIGH
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

CVSS VectorGitHub Advisory

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

Lifecycle Timeline

3
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 - 13:49 nvd
HIGH 8.4

DescriptionGitHub Advisory

EVerest is an EV charging software stack. Prior to version 2026.02.0, an off-by-one check in IsoMux certificate filename handling causes a stack-based buffer overflow when a filename length equals MAX_FILE_NAME_LENGTH (100). A crafted filename in the certificate directory can overflow file_names[idx], corrupting stack state and enabling potential code execution. Version 2026.02.0 contains a patch.

Executive ViewAI

Why It Matters

EVerest-core versions prior to 2026.02.0 contain a stack buffer overflow in the IsoMux component that allows local attackers to execute arbitrary code without authentication when processing specially crafted certificate filenames. This vulnerability directly threatens the integrity and availability of EV charging infrastructure, potentially enabling attackers with local access to compromise charging stations and disrupt service delivery.

Business Impact: High
Compensating Controls

Apply vendor patch to EVerest-core version 2026.02.0 or later. If immediate patching is not feasible, restrict local physical access to affected charging station hardware and monitor for anomalous file processing activities targeting certificate pathways; however, patching is the primary remediation.

Threat Intelligence Overview

EPSS Score
0.0%
Top 99% 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
Scheduled
Exploitation
Poc
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

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.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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-2026-22790 HIGH
8.8 Mar 26

Remote code execution vulnerability in EVerest electric vehicle charging software stack allows adjacent network attacker

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

CVE-2026-26008 HIGH
7.5 Mar 26

Out-of-bounds vector access in EVerest EV charging software (everest-core versions before 2026.02.0) enables remote unau

CVE-2025-68134 HIGH
7.4 Jan 21

EVerest is an EV charging software stack. Prior to version 2025.10.0, the use of the `assert` function to handle errors

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