Skip to main content
VulnerabilityPublished Updated

CVE-2026-33009: everest-core · Race Condition

Affects everest-coreSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% 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:L/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 30 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

A patch is available in EVerest everest-core version 2026.02.0 that fixes the race condition by properly synchronizing access to shared context objects. Users should upgrade to version 2026.02.0 or later to remediate this vulnerability.

Description

CVE-2026-33009 is a high-severity race condition vulnerability in the EVerest everest-core EV charging software stack versions prior to 2026.02.0. The issue arises from concurrent access to shared context objects without proper locking, triggered by a specific MQTT message. This can lead to undefined behavior and potential memory corruption. The vulnerability has been patched in version 2026.02.0.

References

Community reviews

Loading reviews…