CVE-2026-26071: everest everest-core Race Condition
CVSS: 4.2v3.1MediumAnalyzed
Published 26-03-2026Last modified 26-03-2026
Vulnerability summary
CVE-2026-26071 is a medium (CVSS 4.2) Race Condition vulnerability in everest everest-core. EPSS estimates a 0.14% chance of exploitation in the next 30 days, higher than 2.7% of scored vulnerabilities.
CVSS score
4.2/10
010
Medium · v3.1 (CVE.org)EPSS score
0.14%
0%100%
Low · 0.00 pp in 30 daysKEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded
Timeline
- 26-03-2026PublishedVulnerability first disclosed.
- 26-03-2026Last modifiedVulnerability information updated.
Description
EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to `std::string` concurrent access. with heap-use-after-free possible. This is triggered by EVCCID update (EV/ISO15118) and OCPP session/authorization events. Version 2026.02.0 contains a patch.
CVSS metrics
2 scores · 2 sources · 1 versionMedium 4.2Preferred score · CVE.org (CNA)
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HSourcesAll 2 agree
- NVDNIST4.2MediumCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS trend
Probability
0.14%
Chance of exploitation in the next 30 days
Percentile
3%
Versus all other CVEs
30-day change
0.00 pp
From 0.13% on 19-09-2026
19-09-202619-10-2026
EPSS score0.14%
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
- CWE-416Use After FreeThe product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Affected systems
Everest1 product
- everest-core< 2026.02.0
Linuxfoundation1 product
- everest< 2026.02.0
2 vendors · 2 products
References
1 links- github.com/EVerest/EVerest/security/advisories/GHSA-xww8-4hfx-9fjwX Refsource CONFIRMVendor Advisory