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

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

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2026
- **Updated:** 28 Mar 2026
- **Also known as:** GHSA-cpqf-mcqc-783m

## 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 (Off-by-one Error)

## Which versions are affected by CVE-2026-22593?

It affects 1 product.


Products: 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.

## Is CVE-2026-22593 being exploited?

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

## Other vulnerabilities in everest-core

- [CVE-2026-22790](https://insights.sbomify.com/CVE-2026-22790/): EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload (high 8.8)
- [CVE-2026-23995](https://insights.sbomify.com/CVE-2026-23995/): EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ (high 8.4)
- [CVE-2025-68137](https://insights.sbomify.com/CVE-2025-68137/): EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop (high 8.4)
- [CVE-2026-33009](https://insights.sbomify.com/CVE-2026-33009/): EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio (high 8.2)
- [CVE-2026-26008](https://insights.sbomify.com/CVE-2026-26008/): EVerest has OOB via EVSE ID Indexing Mismatch in OCPP 2.0.1 UpdateAllowedEnergyTransferModes (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22593 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22593 exists.

Affected product: everest-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22593/ (Markdown: https://insights.sbomify.com/CVE-2026-22593/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22593
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22593
- OSV: https://osv.dev/vulnerability/CVE-2026-22593

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22593/
Summaries are generated and may contain mistakes; the official description above is the record.