CVE-2026-26073: EVerest is an EV charging software stack

Q: How do I fix CVE-2026-26073?

everest: upgrade to 2026.02.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-26073 being exploited?

CVE-2026-26073 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-26073 affect?

CVE-2026-26073 affects everest. Severity is medium (CVSS 5.9). EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started

Q: How urgent is CVE-2026-26073?

Priority 37/100. Remotely exploitable, no login, no user action; On your watchlist

Routine

MEDIUM 5.9REMOTEWATCHLISTUPGRADE

CVE-2026-26073 is a medium-severity flaw (CVSS 5.9) affecting everest. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started). This results in a TSAN data race report and an ASAN/UBSAN misaligned address runtime error being observed. Version 2026.02.0 contains a patch.

Why this priority

Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-122, CWE-787
Published	2026-03-26
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: linuxfoundation

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-26 17:16 UTCPublished CVE record published
2026-06-17 10:25 UTCUpdated Record last modified

linuxfoundation everest UPGRADE

Affected: < 2026.02.0

Fixed in: 2026.02.0

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-26073?

everest: upgrade to 2026.02.0. Exact commands for each OS are on this page.

Is CVE-2026-26073 being exploited?

CVE-2026-26073 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-26073 affect?

CVE-2026-26073 affects everest. Severity is medium (CVSS 5.9). EVerest is an EV charging software stack. Versions prior to 2026.02.0 have a data race leading to possible `std::queue`/`std::deque` corruption. The trigger is powermeter public key update and EV session/error events (while OCPP not started

How urgent is CVE-2026-26073?

Priority 37/100. Remotely exploitable, no login, no user action; On your watchlist

Related CVEs

CVE-2026-33015 MEDIUM 5.2 UPGRADE EVerest is an EV charging software stack
CVE-2026-33014 MEDIUM 5.2 UPGRADE EVerest is an EV charging software stack
CVE-2026-33009 HIGH 8.2 UPGRADE EVerest is an EV charging software stack
CVE-2026-29044 MEDIUM 5.0 UPGRADE EVerest is an EV charging software stack
CVE-2026-27828 HIGH 7.5 UPGRADE EVerest is an EV charging software stack

References

← Back to latest CVEs