CVE-2026-22593 | EVerest up to 2025.12.0 Filename MAX_FILE_NAME_LENGTH off-by-one
VulDBArchived Mar 26, 2026✓ Full text saved
A vulnerability was found in EVerest up to 2025.12.0 . It has been rated as problematic . Impacted is an unknown function of the component Filename Handler . The manipulation of the argument MAX_FILE_NAME_LENGTH leads to off-by-one. This vulnerability is listed as CVE-2026-22593 . The attack must be carried out locally. There is no available exploit. Upgrading the affected component is advised.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353634 · CVE-2026-22593 · EUVD-2026-16173
EVEREST UP TO 2025.12.0 FILENAME MAX_FILE_NAME_LENGTH OFF-BY-ONE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.7 $0-$5k 3.35+
Summaryinfo
A vulnerability categorized as problematic has been discovered in EVerest. The affected element is an unknown function of the component Filename Handler. The manipulation of the argument MAX_FILE_NAME_LENGTH results in off-by-one. This vulnerability is cataloged as CVE-2026-22593. The attack must be initiated from a local position. There is no exploit available. It is advisable to upgrade the affected component.
Detailsinfo
A vulnerability was found in EVerest. It has been classified as problematic. Affected is an unknown functionality of the component Filename Handler. The manipulation of the argument MAX_FILE_NAME_LENGTH with an unknown input leads to a off-by-one vulnerability. CWE is classifying the issue as CWE-193. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-22593 since 01/07/2026. The exploitability is told to be easy. Local access is required to approach this attack. Technical details 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-16173).
Productinfo
Name
EVerest
Version
2.0.4
2.2.5
3.0.4.2
3.0.8.1
3.0.9
3.0.9.5
5.50.2100
2025.9.0
2025.10.0
2025.12.0
Website
Product: https://github.com/EVerest/EVerest/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.4
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: Off-by-one
CWE: CWE-193 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
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 2026.02.0
Timelineinfo
01/07/2026 CVE reserved
03/26/2026 +78 days Advisory disclosed
03/26/2026 +0 days VulDB entry created
03/26/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-22593 (🔒)
GCVE (CVE): GCVE-0-2026-22593
GCVE (VulDB): GCVE-100-353634
EUVD: 🔒
Entryinfo
Created: 03/26/2026 15:32
Updated: 03/26/2026 16:47
Changes: 03/26/2026 15:32 (63), 03/26/2026 16:47 (1)
Complete: 🔍
Cache ID: 99:27B:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸