Everest
CVE-2025-68139
MEDIUM
Severity by source
AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Lifecycle Timeline
2DescriptionGitHub Advisory
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.
AnalysisAI
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. [CVSS 4.3 MEDIUM]
Technical ContextAI
Classified as CWE-384 (Session Fixation). Affects Everest. 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 vulnerabiliti
RemediationAI
Monitor vendor advisories for a patch.
EVerest is an EV charging software stack. Prior to version 2025.10.0, an integer overflow occurring in `SdpPacket::parse
EVerest is an EV charging software stack. Prior to version 2025.10.0, during the deserialization of a `DC_ChargeLoopRes`
EVerest is an EV charging software stack. Prior to version 2025.10.0, once the module receives a SDP request, it creates
EVerest is an EV charging software stack. In versions 2025.9.0 and below, an attacker can exhaust the operating system's
EVerest is an EV charging software stack. Prior to version 2025.10.0, C++ exceptions are not properly handled for and by
EVerest is an EV charging software stack. Prior to version 2025.12.0, `is_message_crc_correct` in the DZG_GSH01 powermet
Everest EV charging software prior to version 2025.9.0 contains an improper pointer arithmetic flaw in error handling wh
EVerest is an EV charging software stack. Prior to version 2025.10.0, the use of the `assert` function to handle errors
EVerest is an EV charging software stack. [CVSS 4.3 MEDIUM]
EVerest is an EV charging software stack. Prior to version 2025.9.0, once the validity of the received V2G message has b
EVerest EV charging software prior to version 2026.02.0 contains a race condition in concurrent map access that can corr
EVerest EV charging software versions before 2026.02.0 contain a race condition in std::string handling triggered by con
Same weakness CWE-384 – Session Fixation
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today