CVE-2025-68134: CWE-20: Improper Input Validation in EVerest everest-core
CVE-2025-68134 is a high-severity vulnerability in the EVerest everest-core EV charging software stack prior to version 2025. 10. 0. It stems from improper input validation where the use of the assert function causes module crashes. When any module crashes, the manager process shuts down all other modules and exits, leading to a denial of service (DoS) that affects multiple EVSE units and users. The vulnerability does not impact confidentiality or integrity but severely impacts availability. Exploitation requires no privileges or user interaction and can be performed remotely via network access. The issue is fixed in version 2025. 10. 0.
AI Analysis
Technical Summary
CVE-2025-68134 is a vulnerability classified under CWE-20 (Improper Input Validation) affecting the everest-core component of the EVerest EV charging software stack. The root cause is the use of the assert function for error handling in versions prior to 2025.10.0. When invalid input or unexpected conditions trigger an assert failure, the affected module crashes. The EVerest manager process, responsible for orchestrating multiple modules managing Electric Vehicle Supply Equipment (EVSE), is designed to shut down all modules and exit if any single module terminates unexpectedly. This design flaw leads to a cascading failure resulting in a denial of service across all managed EVSE units. The vulnerability can be exploited remotely without authentication or user interaction, as the attack surface includes network-accessible interfaces of the EV charging management system. Although there are no known exploits in the wild as of the publication date, the high CVSS score of 7.4 reflects the significant impact on availability and the ease of exploitation. The vulnerability does not affect confidentiality or integrity, but the complete service disruption can severely impact EV charging operations. The issue is resolved in version 2025.10.0 by replacing assert-based error handling with more resilient mechanisms that prevent the manager from shutting down all modules upon a single module failure.
Potential Impact
For European organizations operating EV charging infrastructure using the affected EVerest everest-core versions, this vulnerability poses a significant risk of widespread denial of service. The cascading shutdown of all EVSE modules managed by the software can disrupt charging services for multiple users simultaneously, potentially causing operational downtime, customer dissatisfaction, and financial losses. Given the increasing reliance on EV infrastructure to meet EU climate goals and the growing EV adoption rates, such disruptions could have broader implications on transportation and energy sectors. Critical infrastructure operators and commercial charging station providers may face reputational damage and regulatory scrutiny if service availability is compromised. Additionally, the vulnerability could be exploited by threat actors aiming to cause disruption or leverage the downtime for further attacks. The lack of confidentiality or integrity impact limits data breach concerns, but availability impact alone is substantial given the essential nature of 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 robust mechanisms preventing manager shutdown on module failure. Organizations should implement rigorous input validation and error handling practices within their EV charging software stacks to avoid similar cascading failures. Network segmentation and access controls should be enforced to limit exposure of management interfaces to untrusted networks. Monitoring and alerting should be enhanced to detect module crashes promptly and enable rapid response before full service disruption occurs. Additionally, operators should conduct regular software audits and vulnerability assessments on EV infrastructure components. In environments where immediate patching is not feasible, temporary mitigations could include isolating vulnerable modules or deploying redundant management systems to maintain service continuity.
Affected Countries
Germany, France, Netherlands, Norway, United Kingdom, Sweden, Belgium
CVE-2025-68134: CWE-20: Improper Input Validation in EVerest everest-core
Description
CVE-2025-68134 is a high-severity vulnerability in the EVerest everest-core EV charging software stack prior to version 2025. 10. 0. It stems from improper input validation where the use of the assert function causes module crashes. When any module crashes, the manager process shuts down all other modules and exits, leading to a denial of service (DoS) that affects multiple EVSE units and users. The vulnerability does not impact confidentiality or integrity but severely impacts availability. Exploitation requires no privileges or user interaction and can be performed remotely via network access. The issue is fixed in version 2025. 10. 0.
AI-Powered Analysis
Technical Analysis
CVE-2025-68134 is a vulnerability classified under CWE-20 (Improper Input Validation) affecting the everest-core component of the EVerest EV charging software stack. The root cause is the use of the assert function for error handling in versions prior to 2025.10.0. When invalid input or unexpected conditions trigger an assert failure, the affected module crashes. The EVerest manager process, responsible for orchestrating multiple modules managing Electric Vehicle Supply Equipment (EVSE), is designed to shut down all modules and exit if any single module terminates unexpectedly. This design flaw leads to a cascading failure resulting in a denial of service across all managed EVSE units. The vulnerability can be exploited remotely without authentication or user interaction, as the attack surface includes network-accessible interfaces of the EV charging management system. Although there are no known exploits in the wild as of the publication date, the high CVSS score of 7.4 reflects the significant impact on availability and the ease of exploitation. The vulnerability does not affect confidentiality or integrity, but the complete service disruption can severely impact EV charging operations. The issue is resolved in version 2025.10.0 by replacing assert-based error handling with more resilient mechanisms that prevent the manager from shutting down all modules upon a single module failure.
Potential Impact
For European organizations operating EV charging infrastructure using the affected EVerest everest-core versions, this vulnerability poses a significant risk of widespread denial of service. The cascading shutdown of all EVSE modules managed by the software can disrupt charging services for multiple users simultaneously, potentially causing operational downtime, customer dissatisfaction, and financial losses. Given the increasing reliance on EV infrastructure to meet EU climate goals and the growing EV adoption rates, such disruptions could have broader implications on transportation and energy sectors. Critical infrastructure operators and commercial charging station providers may face reputational damage and regulatory scrutiny if service availability is compromised. Additionally, the vulnerability could be exploited by threat actors aiming to cause disruption or leverage the downtime for further attacks. The lack of confidentiality or integrity impact limits data breach concerns, but availability impact alone is substantial given the essential nature of 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 robust mechanisms preventing manager shutdown on module failure. Organizations should implement rigorous input validation and error handling practices within their EV charging software stacks to avoid similar cascading failures. Network segmentation and access controls should be enforced to limit exposure of management interfaces to untrusted networks. Monitoring and alerting should be enhanced to detect module crashes promptly and enable rapid response before full service disruption occurs. Additionally, operators should conduct regular software audits and vulnerability assessments on EV infrastructure components. In environments where immediate patching is not feasible, temporary mitigations could include isolating vulnerable modules or deploying redundant management systems to maintain service continuity.
Affected Countries
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/28/2026, 8:25:50 PM
Last updated: 2/5/2026, 1:37:59 PM
Views: 29
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-1517: SQL Injection in iomad
MediumCVE-2026-23572: CWE-863 Incorrect Authorization in TeamViewer Remote
HighCVE-2026-1966: CWE-522 Insufficiently Protected Credentials in YugabyteDB Inc YugabyteDB Anywhere
LowCVE-2026-23797: CWE-256 Plaintext Storage of a Password in OpenSolution Quick.Cart
MediumCVE-2026-23796: CWE-384 Session Fixation in OpenSolution Quick.Cart
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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.