CVE-2025-68139: In EVerest, by default, the EV is responsible for closing the connection if the module encounters an error during request processing

Published Jan 21, 2026
·
Updated

EVerest is an EV charging software stack. In all versions up to and including 2025.12.1, the default value for terminateconnectiononfailedresponse 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 terminateconnectiononfailedresponse 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 Software

2 affected components
Everest EVerest<=2025.12.1
linuxfoundation Everest<=2025.12.1

Event History

Jan 21, 2026
CVE Published
via MITRE·07:36 PM
Data Sourced
via MITRE·07:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-68139?

CVE-2025-68139 is classified as a moderate severity vulnerability due to the potential for connection issues during error handling in the EVerest software.

2

How do I fix CVE-2025-68139?

To fix CVE-2025-68139, update to the latest version of EVerest beyond 2025.12.1 where the issue is resolved.

3

What is the impact of CVE-2025-68139?

The impact of CVE-2025-68139 involves the risk of persistent connections remaining open after failed requests, which can lead to resource exhaustion.

4

Which versions of EVerest are affected by CVE-2025-68139?

All versions of EVerest up to and including 2025.12.1 are affected by CVE-2025-68139.

5

Is CVE-2025-68139 a remote code execution vulnerability?

No, CVE-2025-68139 is not a remote code execution vulnerability but rather a connection management issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203