EVerest everest-core 2025.9.0 unique_ptr allocation of resources

Summaryinfo

A vulnerability, which was classified as critical, has been found in EVerest everest-core. This affects an unknown part. The manipulation of the argument unique_ptr leads to allocation of resources. This vulnerability is referenced as CVE-2025-68136. The attack needs to be initiated within the local network. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in EVerest everest-core. This issue affects an unknown functionality. The manipulation of the argument unique_ptr with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:

EVerest is an EV charging software stack. Prior to version 2025.10.0, once the module receives a SDP request, it creates a whole new set of objects like `Session`, `IConnection` which open new TCP socket for the ISO15118-20 communications and registers callbacks for the created file descriptor, without closing and destroying the previous ones. Previous `Session` is not saved and the usage of an `unique_ptr` is lost, destroying connection data. Latter, if the used socket and therefore file descriptor is not the last one, it will lead to a null pointer dereference. Version 2025.10.0 fixes the issue.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-68136 since 12/15/2025. The exploitation is known to be easy. The attack can only be done within the local network. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

Upgrading to version 2025.10.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-206318). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• EVerest

Name

• everest-core

Version

• 2025.9.0

Website

• Product: https://github.com/EVerest/everest-core/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion