Skip to main content
VulnerabilityPublished

CVE-2025-68141: everest-core · NULL Pointer Dereference

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.2% chance of exploitation in 30 days – higher than 20% 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 the EVerest everest-core software to version 2025.10.0 or later, where the vulnerability is fixed. Organizations should prioritize patching affected systems to prevent exploitation. In parallel, network segmentation should be implemented to isolate EV charging management systems from untrusted networks, reducing the attack surface. Deploying strict input validation and anomaly detection on incoming DC_ChargeLoopRes messages can help identify and block malformed or suspicious payloads that might trigger the vulnerability. Monitoring logs and process health of EVerest modules can provide early warning of crashes or abnormal terminations. Employing redundancy and failover mechanisms in EVSE management can minimize service disruption if a module crashes. Finally, coordinating with EVerest vendors for security advisories and updates will ensure timely awareness of related vulnerabilities.

Description

CVE-2025-68141 is a high-severity vulnerability in the EVerest everest-core EV charging software stack prior to version 2025.10.0. It involves a NULL pointer dereference triggered during deserialization of a DC_ChargeLoopRes message containing Receipt and TaxCosts data. Specifically, an out-of-bounds access occurs in the convert function handling DetailedTaxType, causing the module and all EVerest processes to terminate, resulting in denial of service for EV charging stations. Exploitation requires network access but no authentication or user interaction. The vulnerability impacts availability but not confidentiality or integrity. The issue is fixed in version 2025.10.0.

References

Community reviews

Loading reviews…