🛡️ CVE-2026-26072 — everest

🟡 CVSS 4.2 — Medium ✅ No Known Exploit CWE-362 NVD
4.2
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to std::map<std::optional> concurrent access (container/optional corruption possible). The trigger is EV SoC update with powermeter periodic update and unplugging/SessionFinished status. Version 2026.02.0 patches the issue.

How this vulnerability can be exploited

This issue can be reached with physical access to the device, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Weakness class

CVE-2026-26072 is classified as CWE-362: Race Condition. Concurrent operations share state without proper synchronisation, so timing decides whether the result is correct.

Affected software

CVE-2026-26072 is recorded against 1 package.

  • everest (fixed in 2026.02.0)

Timeline and source

Published on 26 March 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com

Details

Severity MEDIUM
CVSS Score 4.2
CVSS Vector CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE CWE-362
Public Exploit ✅ No
Source NVD
Published 2026-03-26
Updated 2026-08-11
Modified 2026-06-17
Fix URL N/A

Affected Packages

Software From version Fixed in
everest 2026.02.0

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in everest

CVE-2026-26072 is rated CVSS 4.2 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.