Charger crash via unsynchronized EVCCID access
Published Mar 26, 2026 · Updated Mar 26, 2026
Data race in EVerest Core before 2026.02.0 allows physically proximate attackers to crash the charging service via EVCCID events. The OCPP201 module reads and writes evse_evcc_id string values from session-processing and EVInfo callback threads without locking, allowing heap use-after-free. Exploitation requires physical EV interaction timed with OCPP session or authorization processing and interrupts EVSE availability.
Summary
What happened
Data race in EVerest Core before 2026.02.0 allows physically proximate attackers to crash the charging service via EVCCID events. The OCPP201 module reads and writes evse_evcc_id string values from session-processing and EVInfo callback threads without locking, allowing heap use-after-free. Exploitation requires physical EV interaction timed with OCPP session or authorization processing and interrupts EVSE availability.
The record
- CVE
- CVE-2026-26071
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- EVerest
- Product
- EVerest Core
- Classifications
- CWE-416, CWE-362, T1499
- Attack vector
- physical
- 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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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