CVE-2025-68135 Details
Description
EVerest is an EV charging software stack. Prior to version 2025.10.0, C++ exceptions are not properly handled for and by the `TbdController` loop, leading to its caller and itself to silently terminates. Thus, this leads to a denial of service as it is responsible of SDP and ISO15118-20 servers. Version 2025.10.0 fixes the issue.
A denial-of-service vulnerability has been identified in EVerest, an EV charging software stack, prior to version 2025.10.0. The issue arises from improper handling of C++ exceptions in the TbdController loop, which is responsible for managing SDP and ISO15118-20 servers. When an unhandled exception occurs, the loop and its caller terminate silently, causing the module to become unusable and disrupting server functionality.
Users can upgrade to EVerest version 2025.10.0 or later, where this vulnerability has been addressed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 21, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/EVerest/everest-core/security/advisories/GHSA-g7mm-r6qp-96vh | [email protected] | ExploitVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-703 | Improper Check or Handling of Exceptional Conditions | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linuxfoundation everest | < 2025.10.0 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 6, 2026 | Initial Analysis | [email protected] |
| Jan 21, 2026 | CVE Modified | [email protected] |
| Jan 21, 2026 | New CVE Received | [email protected] |