Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-68134: CWE-20: Improper Input Validation in EVerest everest-core

0
High
VulnerabilityCVE-2025-68134cvecve-2025-68134cwe-20
Published: Wed Jan 21 2026 (01/21/2026, 18:32:13 UTC)
Source: CVE Database V5
Vendor/Project: EVerest
Product: everest-core

Description

EVerest is an EV charging software stack. Prior to version 2025.10.0, the use of the `assert` function to handle errors frequently causes the module to crash. This is particularly critical because the manager shuts down all other modules and exits when any one of them terminates, leading to a denial of service. In a context where a manager handles multiple EVSE, this would also impact other users. Version 2025.10.0 fixes the issue.

AI-Powered Analysis

AILast updated: 01/21/2026, 19:05:23 UTC

Technical Analysis

CVE-2025-68134 is a vulnerability classified under CWE-20 (Improper Input Validation) affecting the EVerest everest-core software, a critical component of the EVerest EV charging software stack. The root cause is the inappropriate use of the assert function for error handling in versions prior to 2025.10.0. When invalid input triggers an assertion failure, the affected module crashes. The EVerest manager process, responsible for orchestrating multiple EVSE (Electric Vehicle Supply Equipment) modules, is designed to shut down all modules and exit if any single module terminates unexpectedly. This design flaw leads to a cascading denial of service, impacting all EVSE managed by the system and thereby multiple users simultaneously. The vulnerability does not compromise confidentiality or integrity but severely impacts availability. Exploitation requires no privileges or user interaction, and the attack vector is network-based (AV:A - adjacent network). The CVSS v3.1 base score is 7.4 (high), reflecting the ease of exploitation and the broad impact on availability and system scope (S:C - changed scope). Although no exploits have been reported in the wild, the vulnerability is critical for operators of EV charging infrastructure. The fix was introduced in version 2025.10.0 by replacing assert-based error handling with more resilient input validation and error management mechanisms.

Potential Impact

For European organizations operating EV charging infrastructure using EVerest everest-core, this vulnerability can cause widespread denial of service, disrupting EV charging availability for multiple users simultaneously. This can lead to operational downtime, customer dissatisfaction, and potential financial losses, especially in regions with high EV adoption. The cascading shutdown of modules affects the reliability and availability of charging stations, which are critical for supporting Europe’s transition to sustainable transportation. Additionally, service outages could impact public perception and trust in EV infrastructure providers. In critical urban areas or along major transit corridors, such disruptions could have broader economic and mobility consequences. Since the vulnerability does not affect confidentiality or integrity, data breaches or manipulation are not a concern here, but the availability impact alone is significant given the reliance on EV charging services.

Mitigation Recommendations

The primary mitigation is to upgrade all affected EVerest everest-core installations to version 2025.10.0 or later, where the assert-based error handling has been replaced with proper input validation and robust error management. Organizations should audit their EVSE management systems to identify any instances running vulnerable versions. Additionally, implement network segmentation and monitoring to detect abnormal module terminations or crashes that could indicate exploitation attempts. Employ rigorous input validation at all interfaces exposed to network inputs to prevent malformed data from triggering assertion failures. Consider deploying redundancy and failover mechanisms in the EVSE management architecture to minimize service disruption if a module fails. Regularly review and test error handling logic in critical software components to avoid similar single points of failure. Finally, maintain up-to-date incident response plans tailored to EV infrastructure outages.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-15T18:09:12.694Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 697120104623b1157ce4b45b

Added to database: 1/21/2026, 6:50:56 PM

Last enriched: 1/21/2026, 7:05:23 PM

Last updated: 1/21/2026, 11:51:46 PM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats