Local code execution via off-by-one filename copy
Published Mar 26, 2026 · Updated Mar 26, 2026
Stack buffer overflow in EVerest Core before 2026.02.0 allows local users to execute code via a crafted certificate filename. The get_dir_numbered_file_names function accepts a 100-byte directory entry, then strcpy copies 101 bytes including the terminator into file_names[idx]. Control of a filename in the PKI or CA directory is the required local gate; successful stack corruption crashes IsoMux or executes code in its process context.
Summary
What happened
Stack buffer overflow in EVerest Core before 2026.02.0 allows local users to execute code via a crafted certificate filename. The get_dir_numbered_file_names function accepts a 100-byte directory entry, then strcpy copies 101 bytes including the terminator into file_names[idx]. Control of a filename in the PKI or CA directory is the required local gate; successful stack corruption crashes IsoMux or executes code in its process context.
The record
- CVE
- CVE-2026-22593
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- EVerest
- Product
- EVerest Core
- Classifications
- CWE-193, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2026.02.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- IsoMux 100-byte filename AddressSanitizer reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo