# CVE-2026-26074: EVerest: OCPP201 startup event_queue lock mismatch leads to std::map/std::queue data race

> A data race in EVerest EV charging software can corrupt internal queues, potentially causing denial of service when specific network and physical events coincide.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-p3hg-vqgv-h524

## What is CVE-2026-26074?

CVE-2026-26074 is a high-severity vulnerability in everest-core, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::map<std::queue>` corruption. The trigger is CSMS GetLog/UpdateFirmware request (network) with an EVSE fault event (physical). This results in TSAN reports concurrent access (data race) to `event_queue`. Version 2026.2.0 contains a patch.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-26074?

It affects 1 product.


Products: Linuxfoundation Everest.

## How do I fix CVE-2026-26074?

No fix has been published for CVE-2026-26074 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26074 being exploited?

There is no known exploitation of CVE-2026-26074 in the wild and no public exploit code.

## Other vulnerabilities in everest-core

- [CVE-2026-22790](https://insights.sbomify.com/CVE-2026-22790/): EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload (high 8.8)
- [CVE-2026-22593](https://insights.sbomify.com/CVE-2026-22593/): EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing (high 8.4)
- [CVE-2026-23995](https://insights.sbomify.com/CVE-2026-23995/): EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ (high 8.4)
- [CVE-2025-68137](https://insights.sbomify.com/CVE-2025-68137/): EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop (high 8.4)
- [CVE-2026-33009](https://insights.sbomify.com/CVE-2026-33009/): EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26074 and fix it if it is affected.

What it is: CVE-2026-26074 is a high-severity vulnerability in everest-core, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26074 in the wild and no public exploit code.

Affected product: everest-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26074/ (Markdown: https://insights.sbomify.com/CVE-2026-26074/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26074
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26074
- OSV: https://osv.dev/vulnerability/CVE-2026-26074

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26074/
Summaries are generated and may contain mistakes; the official description above is the record.