CVE-2025-68139
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 5% of all known CVEs.
References
Related Vulnerabilities
Other CWE-384 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2018-11714 | Critical | 9.8 | 32% | - | - |
| CVE-2019-12258 | High | 7.5 | 23% | - | Fix |
| CVE-2019-10008 | High | 8.8 | 22% | - | - |
| CVE-2018-17199 | High | 7.5 | 21% | - | Fix |
| CVE-2024-50339 | Medium | 5.3 | 20% | - | Fix |
| CVE-2018-18925 | Critical | 9.8 | 18% | - | - |
Common questions
How do I fix CVE-2025-68139?
No published fix for CVE-2025-68139 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2025-68139 being actively exploited?
Not that we know of. CVE-2025-68139 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.15% is the estimated probability that it will be exploited in the next 30 days. That is higher than 5% of all scored CVEs.
How severe is CVE-2025-68139?
CVE-2025-68139 has a CVSS v3 base score of 4.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2025-68139
Markdown
[](https://tridentstack.com/cve/CVE-2025-68139)HTML
<a href="https://tridentstack.com/cve/CVE-2025-68139"><img src="https://tridentstack.com/cve/badge/CVE-2025-68139.svg" alt="CVE-2025-68139"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-02-06.