CVE-2026-22593: high-severity vulnerability in everest-core
EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.4epss 0.1%
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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
EVerest · everest-coreRelated CVEs — everest-core
In the same product, most dangerous first.
CVE-2025-68137HIGHEVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loopEPSS 1.3%CVE-2024-37310CRITICALEVerest has an integer overflow in the "v2g_incoming_v2gtp" function EPSS 0.7%CVE-2026-22790HIGHEVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payloadEPSS 0.6%CVE-2025-68133HIGHEVerest's unlimited connections can lead to DoS through operating system resource exhaustionEPSS 0.4%CVE-2026-26008HIGHEVerest has OOB via EVSE ID Indexing Mismatch in OCPP 2.0.1 UpdateAllowedEnergyTransferModesEPSS 0.4%CVE-2025-68135MEDIUMEVerest's inadequate exception handling leads to denial of serviceEPSS 0.3%