CVE-2025-68139
BaseFortify
Publication date: 2026-01-21
Last updated on: 2026-02-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linuxfoundation | everest | to 2025.12.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-384 | Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in EVerest (everest-core) involves the default setting of the parameter `terminate_connection_on_failed_response` being set to false. This means that when an error occurs during a Vehicle-to-Grid communication session, the module does not automatically terminate the session or connection. Instead, the responsibility to close the session lies with the Electric Vehicle (EV). Because errors are only logged and no countermeasures like session resets or connection termination are triggered, a malicious user could exploit this behavior to leverage other weaknesses or vulnerabilities in the system. Changing the setting to true would cause immediate termination of the connection on failed responses, mitigating the risk, but this is not the default due to potential negative impacts on vehicle ECUs. [1]
How can this vulnerability impact me? :
This vulnerability could allow a malicious user to exploit unhandled errors in the communication session between the EV and the charging system. Because the module does not terminate connections on failed responses by default, attackers might leverage this to exploit other weaknesses or vulnerabilities, potentially compromising the integrity of the system. However, the impact is rated as moderate with low integrity impact and no confidentiality or availability impact. The main risk is that the system could be manipulated through these unhandled errors, but it does not directly cause data breaches or service outages. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves monitoring the configuration parameter `terminate_connection_on_failed_response` in the EVerest software stack. If this parameter is set to false, the system is vulnerable. Additionally, monitoring logs for repeated failed response codes without session termination may indicate exploitation attempts. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to change the configuration parameter `terminate_connection_on_failed_response` from false to true. This causes the module to terminate the V2G connection immediately upon a failed response, preventing exploitation. However, this may cause errors in vehicle ECUs and require ECU resets, leading to temporary unavailability of charging services. There are no patched versions currently available. [1]