Remote crash via one-based EVSE vector indexing
Published Mar 26, 2026 · Updated Mar 26, 2026
Out-of-bounds access in EVerest Core before 2026.02.0 allows remote attackers to crash charging-station software over OCPP. The OCPP 2.0.1 UpdateAllowedEnergyTransferModes callback uses a 1-based EVSE ID directly to index the 0-based r_evse_manager vector, reading past its end for the last EVSE. A CSMS that can send the message needs no charger-side user interaction; the demonstrated consequence is a heap-buffer-overflow crash, not data disclosure or modification.
Summary
What happened
Out-of-bounds access in EVerest Core before 2026.02.0 allows remote attackers to crash charging-station software over OCPP. The OCPP 2.0.1 UpdateAllowedEnergyTransferModes callback uses a 1-based EVSE ID directly to index the 0-based r_evse_manager vector, reading past its end for the last EVSE. A CSMS that can send the message needs no charger-side user interaction; the demonstrated consequence is a heap-buffer-overflow crash, not data disclosure or modification.
The record
- CVE
- CVE-2026-26008
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- EVerest
- Product
- EVerest Core
- Classifications
- CWE-125, T1499.004
- Attack vector
- network
- 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
- UpdateAllowedEnergyTransferModes ASAN crash reproductionproof 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