Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

CVSS 4.3 · Medium EPSS 0.04% · P13
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-68139

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
In EVerest, by default, the EV is responsible for closing the connection if the module encounters an error during request processing
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source: NVD (National Vulnerability Database)
Vulnerability Type
会话固定
Source: NVD (National Vulnerability Database)
Vulnerability Title
everest-core 授权问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
everest-core是EVerest开源的一个电动汽车充电软件堆栈的主要部分。 everest-core 2025.12.1及之前版本存在授权问题漏洞,该漏洞源于terminate_connection_on_failed_response默认配置为False,可能导致恶意用户利用其他弱点或漏洞。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
EVeresteverest-core <= 2025.12.1 -

II. Public POCs for CVE-2025-68139

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-68139

登录查看更多情报信息。

Same Patch Batch · EVerest · 2026-01-21 · 11 CVEs total

CVE-2025-681378.4 HIGHEVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer o
CVE-2025-681337.4 HIGHEVerest's unlimited connections can lead to DoS through operating system resource exhausti
CVE-2025-681347.4 HIGHEVerest's use of assert functions can potentially lead to denial of service
CVE-2025-681367.4 HIGHEVerest's inadequate session handling can lead to memory-related errors or exhaustion of t
CVE-2025-681417.4 HIGHEVerest vulnerable to null pointer dereference during DC_ChargeLoopRes document deserializ
CVE-2025-681356.5 MEDIUMEVerest's inadequate exception handling leads to denial of service
CVE-2025-681384.7 MEDIUMEVerest affected by memory exhaustion in libocpp
CVE-2025-681404.3 MEDIUMEVerest allows null session ID to bypass session ID verification
CVE-2026-239554.2 MEDIUMEVerest vulnerable to concatenation of strings literal and integers
CVE-2025-68132EVerest has out-of-bounds read in DZG_GSH01 SLIP CRC parser that can crash powermeter driv

IV. Related Vulnerabilities

V. Comments for CVE-2025-68139

No comments yet


Leave a comment