Cyber Resilience

CVE-2026-22593

Linuxfoundation Everest ≤ 2026.02.0

Public PoC
Published
26 March 2026
Modified
31 March 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0014 4th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2026-22593 is a high-severity Off-by-one Error (CWE-193) vulnerability in Linuxfoundation Everest. Its CVSS base score is 8.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-22593 is a stack-based buffer overflow vulnerability in EVerest, an open-source EV charging software stack. Prior to version 2026.02.0, an off-by-one check in the IsoMux component's certificate filename handling triggers the overflow when a filename length equals MAX_FILE_NAME_LENGTH (100). A crafted filename placed in the certificate directory can overflow the file_names[idx] array, corrupting adjacent stack state and enabling potential arbitrary code execution. The issue is classified under CWE-193 (Off-by-One Error) with a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

A local attacker can exploit this vulnerability with low complexity and no privileges or user interaction required. By controlling a filename in the relevant certificate directory, the attacker can manipulate stack memory, leading to crashes or code execution in the context of the EVerest process. The unchanged scope indicates impacts remain within the affected component, but high confidentiality, integrity, and availability effects make it severe for systems running vulnerable versions.

The official GitHub security advisory (GHSA-cpqf-mcqc-783m) documents the flaw, and EVerest version 2026.02.0 includes a patch to address the off-by-one check in filename handling. Security practitioners should upgrade to this version or later and review certificate directory access controls to prevent crafted filenames from being introduced.

EU & UK References

Vulnerability Data

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…

more

`file_names[idx]`, corrupting stack state and enabling potential code execution. Version 2026.02.0 contains a patch.

CWE(s)
CWE-193

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-26071Same product: Linuxfoundation Everest
CVE-2026-27828Same product: Linuxfoundation Everest
CVE-2026-23995Same product: Linuxfoundation Everest
CVE-2026-27813Same product: Linuxfoundation Everest
CVE-2026-22790Same product: Linuxfoundation Everest
CVE-2025-68132Same product: Linuxfoundation Everest
CVE-2026-26008Same product: Linuxfoundation Everest
CVE-2026-27815Same product: Linuxfoundation Everest
CVE-2026-26073Same product: Linuxfoundation Everest
CVE-2025-68135Same product: Linuxfoundation Everest

Affected Assets

linuxfoundation
everest
≤ 2026.02.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.2.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover off-by-one errors in loops, bounds, and calculations before deployment.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can embed bounds-checking and arithmetic-correctness rules that stop off-by-one mistakes at introduction.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent off-by-one errors via reviews, static analysis, and testing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect off-by-one errors before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes requirements and reviews that can catch off-by-one errors.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify bounds-checking and input validation to prevent off-by-one errors.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles promote defensive coding practices that reduce off-by-one mistakes.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses off-by-one errors through coding standards and peer review.

References