Vulnerability · Published Jan 21, 2026 · Assigned by GitHub_M
CVE-2025-68139In EVerest, by default, the EV is responsible for closing the connection if the module encounters an error during request processing
Medium 4.3
In plain English
A medium-severity session fixation in everest-core from EVerest. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities).
Official description
EVerest is an EV charging software stack. In all versions up to and including 2025.12.1, the default value for `terminate_connection_on_failed_response` is `False`, which leaves the responsibility for session and connection termination to the EV. In this configuration, any errors encountered by the module are logged but do not trigger countermeasures such as session and connection reset or termination. This could be abused by a malicious user in order to exploit other weaknesses or vulnerabilities. While the default will stay at the setting that is described as potentially problematic in this reported issue, a mitigation is available by changing the `terminate_connection_on_failed_response` setting to `true`. However this cannot be set to this value by default since it can trigger errors in vehicle ECUs requiring ECU resets and lengthy unavailability in charging for vehicles. The maintainers judge this to be a much more important workaround then short-term unavailability of an EVSE, therefore this setting will stay at the current value.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| EVerest | everest-core | <= 2025.12.1 |
Weakness: CWE-384 · Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
References
- https://github.com/EVerest/everest-core/security/advisories/GHSA-wqh4-pj54-6xv9 x_refsource_CONFIRM