Skip to main content
VulnerabilityPublished

CVE-2026-26008: everest-core · Out-of-bounds Read

Affects everest-coreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2026.02.0 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.02.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade everest-core and everest/everest-core to 2026.02.0.

Affected software

ProductAffectedFixed in
EVeresteverest-coreAffected
  • <2026.02.0
Fixed in
  • 2026.02.0
GitHubeverest/everest-corepkg:github/everest/everest-coreOther threatsAffected
  • <2026.02.0
Fixed in
  • 2026.02.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade all instances of the EVerest everest-core software to version 2026.02.0 or later, where the out-of-bounds read vulnerability has been patched. Network-level controls should be implemented to restrict and monitor traffic from Charging Station Management Systems (CSMS) to the everest-core components, limiting exposure to untrusted sources. Employing intrusion detection systems (IDS) to detect anomalous UpdateAllowedEnergyTransferModes messages could provide early warning of exploitation attempts. Regularly auditing and testing EV charging infrastructure software for memory safety issues is recommended to prevent similar vulnerabilities. Additionally, organizations should maintain an incident response plan tailored to EV infrastructure disruptions to minimize downtime in case of exploitation. Vendors should consider adopting safer coding practices, such as bounds-checked container access or static analysis tools, to prevent future out-of-bounds vulnerabilities.

Description

EVerest is an EV charging software stack. Versions prior to 2026.02.0 have an out-of-bounds access (std::vector) that leads to possible remote crash/memory corruption. This is because the CSMS sends UpdateAllowedEnergyTransferModes over the network. Version 2026.2.0 contains a patch.

References

Community reviews

Loading reviews…