CVE-2026-26070

Charge point crash via unsynchronized SoC map access

Published Mar 26, 2026 · Updated Mar 26, 2026

Race condition in EVerest Core before 2026.02.0 allows physically proximate attackers to crash the charge point by unplugging an EV. The OCPP201 module reads, writes, and resets evse_soc_map from concurrent powermeter, EVInfo, and SessionFinished paths without a mutex. Exploitation requires an EV SoC update, a periodic powermeter update, and an unplug event; the resulting bad optional access terminates the process.

CVSS severity4.6
Medium
EPSS probability0.10%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in EVerest Core before 2026.02.0 allows physically proximate attackers to crash the charge point by unplugging an EV. The OCPP201 module reads, writes, and resets evse_soc_map from concurrent powermeter, EVInfo, and SessionFinished paths without a mutex. Exploitation requires an EV SoC update, a periodic powermeter update, and an unplug event; the resulting bad optional access terminates the process.

The record

CVE
CVE-2026-26070
Published
Mar 26, 2026
Updated
Mar 26, 2026
Vendor
EVerest
Product
EVerest Core
Classifications
CWE-362, T1499
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 26, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=< 2026.02.0

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

EVerest · EVerest Coreversion=< 2026.02.0

Published CVSS scores

4.2NIST NVDCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
4.6GitHub, Inc.CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
T1499Endpoint Denial of Service

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