Skip to main content
VulnerabilityPublished

CVE-2025-68133: everest-core · Unthrottled Resource Allocation

Affects everest-coreSource CVE Database V5

0

Not known to be exploited · CVSS 7.4 High : upgrade to 2025.10.0 soon.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

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

Affected software

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

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

AI-suggested

The primary mitigation is to upgrade all affected EVerest everest-core installations to version 2025.10.0 or later, where the vulnerability is fixed. Until upgrades can be applied, organizations should implement network-level protections such as rate limiting and connection throttling on the ports used by EVerest to prevent excessive simultaneous connections from single or distributed sources. Deploying intrusion detection or anomaly detection systems to monitor for unusual connection patterns indicative of an attack can provide early warning. Additionally, configuring firewall rules to restrict access to trusted IP ranges or authenticated clients can reduce exposure. Operators should also ensure robust logging and alerting on process crashes or resource exhaustion events to enable rapid incident response. Finally, coordinating with EVSE manufacturers and software vendors for timely patch deployment and security advisories is essential.

Description

EVerest is an EV charging software stack. In versions 2025.9.0 and below, an attacker can exhaust the operating system's memory and cause the module to terminate by initiating an unlimited number of TCP connections that never proceed to ISO 15118-2 communication. This is possible because a new thread is started for each incoming plain TCP or TLS socket connection before any verification occurs, and the verification performed is too permissive. The EVerest processes and all its modules shut down, affecting all EVSE functionality. This issue is fixed in version 2025.10.0.

References

Community reviews

Loading reviews…