CVE-2025-68136
Published: 21 January 2026
Summary
CVE-2025-68136 is a high-severity Allocation of Resources Without Limits or Throttling (CWE-770) vulnerability in Linuxfoundation Everest. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 14.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Threat & Defense at a Glance
Threat & Defense Details
Likely Mitigating ControlsAI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
This control implements explicit throttling on session allocation, addressing the weakness of allocating resources without limits.
Plan testing exercises resource allocation limits and throttling during simulated failures, directly addressing weaknesses that allow unbounded resource use.
Contingency plan updates ensure recovery strategies address unbounded resource allocation, making it harder for attackers to exploit lack of throttling to cause prolonged outages.
Provides continuity when unbounded resource allocation at the primary site leads to exhaustion and downtime.
Alternate services allow operations to continue when primary allocation of resources lacks limits or throttling.
Explicit planning of security-related actions requires defining limits, windows, and resource allocations, making allocation without throttling far less likely.
Measures of performance include tracking allocation behavior and throttling effectiveness, reducing the window for resource exhaustion attacks.
Imposes an inactivity-based limit on network resource allocation, throttling the number of concurrently held connections.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Null pointer dereference in SDP request handler directly enables application crash via crafted network request (T1499.004 Application or System Exploitation).
NVD Description
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…
more
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.
Deeper analysisAI
CVE-2025-68136 is a null pointer dereference vulnerability (CWE-770) in the EVerest EV charging software stack, affecting versions prior to 2025.10.0. The flaw resides in the module handling SDP requests for ISO15118-20 communications. Upon receiving an SDP request, the module instantiates new Session and IConnection objects, opens a new TCP socket, and registers callbacks for the associated file descriptor without closing or destroying the prior ones. The previous Session is not preserved, leading to the loss of its unique_ptr and destruction of connection data. If the socket's file descriptor is not the last one, this triggers a null pointer dereference.
Attackers on an adjacent network (AV:A) can exploit the vulnerability with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). Successful exploitation changes scope (S:C) and causes high-impact availability disruption (A:H) with no confidentiality or integrity effects (C:N/I:N), resulting in a denial of service through application crash. The CVSS v3.1 base score is 7.4.
The GitHub security advisory (GHSA-4h8h-x5cp-g22r) at https://github.com/EVerest/everest-core/security/advisories/GHSA-4h8h-x5cp-g22r confirms the issue and states that version 2025.10.0 resolves it by addressing the object management and file descriptor handling. Security practitioners should prioritize upgrading affected EVerest deployments.
Details
- CWE(s)