CVE-2026-22593 EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing

High 8.4 Published Updated

An off-by-one error in EVerest allows attackers to trigger a stack buffer overflow via crafted filenames, potentially leading to code execution.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-22593?

CVE-2026-22593 is a high-severity memory corruption vulnerability in everest-core, published on 26 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Weakness: CWE-193

Which versions are affected by CVE-2026-22593?

It affects 1 product.

Products include Linuxfoundation Everest.

How do I fix CVE-2026-22593?

No fix has been published for CVE-2026-22593 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-22593 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22593 exists.

Sources

Also known as GHSA-cpqf-mcqc-783m.

Is CVE-2026-22593 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free