CVE-2026-26074
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEVerest 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEVerest EV charging stack versions before 2026.02.0 have a data race vulnerability in the event_queue (std::map<std::queue>) where concurrent access from network-based CSMS requests (GetLog/UpdateFirmware) and physical EVSE fault events causes potential memory corruption, confirmed by Thread Sanitizer (TSAN) reports.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.02.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed EVerest versionCheck the installed EVerest version by querying the package manager, examining the binary with --version flag, or reading version files in /opt/everest or /usr/local/everest if those paths exist. Use command: dpkg -l | grep everest or rpm -qa | grep everest, or check the CMake configuration file.Affected if version is present and less than 2026.02.0 (e.g., 2025.x, 2024.x, or any version before 2026.02.0)
-
Locate EVerest configuration filesFind the EVerest configuration directory, typically in /etc/everest, /opt/everest/config, or within the deployment directory. Look for main.cpp in the EVerest source or the config/runtime.yaml configuration file that defines enabled modules.Affected if configuration files exist and show EVerest deployment (indicates the product is in use)
-
Verify event_queue module is loadedExamine the EVerest configuration for the event_queue module entry. Search the configuration for 'event_queue' or check the module loading section. If source is available, examine the code for std::map<std::queue> usage in event_queue component.Affected if event_queue module appears in the loaded configuration or std::map<std::queue> is used in event_queue code
-
Confirm CSMS network interface is enabledCheck EVerest configuration for CSMS (Charging Station Management System) settings. Look for ocpp, websocket, or CSMS-related configuration sections. Verify that GetLog and UpdateFirmware operations are available through the OCPP/CSMS interface.Affected if CSMS/OCPP interface is enabled and GetLog/UpdateFirmware commands are accessible via network
-
Check if EVSE fault handling is activeExamine the hardware adapter or EVSE module configuration to confirm fault event handling is enabled. Look for fault_event, error_handling, or EVSE-related fault callback configurations in the EVerest setup.Affected if EVSE fault event handling is configured and active in the deployment
-
Review for Thread Sanitizer evidenceSearch system logs, build logs, or testing reports for Thread Sanitizer (TSAN) output related to event_queue. If you have access to build environment, check if the binary was compiled with -fsanitize=thread and review any TSAN reports.Affected if TSAN reports show data races involving event_queue, std::map, or std::queue with concurrent CSMS and fault event access patterns
The environment is affected if EVerest version is below 2026.02.0 AND both the event_queue module AND CSMS network interface AND EVSE fault handling are simultaneously enabled, creating the concurrent access condition described in the CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.02.0
Upgrade to EVerest version 2026.2.0 or later which includes the patch for proper synchronization around event_queue access. The fix requires adding mutex/lock protection to all concurrent access paths to prevent the race condition.
2026.02.0
- 1. Identify the current EVerest installation version by checking the version identifier in your deployment
- 2. If running any version prior to 2026.02.0, plan for an upgrade to version 2026.02.0 or later
- 3. Backup any existing configuration and data before performing the upgrade
- 4. Obtain EVerest version 2026.02.0 from the official repository or release distribution channel
- 5. Follow the standard upgrade procedure for EVerest, ensuring services are properly stopped before the upgrade
- 6. After upgrade, restart the EVerest services and verify proper operation
- 7. Monitor the system to confirm the data race condition is resolved and no std::map corruption occurs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data