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-68132: CWE-125: Out-of-bounds Read in EVerest everest-core

0
Low
VulnerabilityCVE-2025-68132cvecve-2025-68132cwe-125
Published: Wed Jan 21 2026 (01/21/2026, 18:28:40 UTC)
Source: CVE Database V5
Vendor/Project: EVerest
Product: everest-core

Description

EVerest is an EV charging software stack. Prior to version 2025.12.0, `is_message_crc_correct` in the DZG_GSH01 powermeter SLIP parser reads `vec[vec.size()-1]` and `vec[vec.size()-2]` without checking that at least two bytes are present. Malformed SLIP frames on the serial link can reach `is_message_crc_correct` with `vec.size() < 2` (only via the multi-message path), causing an out-of-bounds read before CRC verification and `pop_back` underflow. Therefore, an attacker controlling the serial input can reliably crash the process. Version 2025.12.0 fixes the issue.

AI-Powered Analysis

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

Technical Analysis

CVE-2025-68132 is a vulnerability classified as CWE-125 (Out-of-bounds Read) found in the EVerest everest-core software stack, which is used in electric vehicle (EV) charging systems. The issue resides in the function is_message_crc_correct within the DZG_GSH01 powermeter SLIP parser. This function attempts to read the last two bytes of a vector (vec[vec.size()-1] and vec[vec.size()-2]) without first verifying that the vector contains at least two bytes. Under normal operation, this assumption holds, but when malformed SLIP frames are received via the serial link—specifically through the multi-message path—the vector size can be less than two. This leads to an out-of-bounds read and a pop_back underflow, which can cause the process to crash. The vulnerability does not require any privileges, user interaction, or network access beyond the serial interface, and it does not compromise confidentiality, integrity, or availability beyond causing a denial of service by crashing the process. The flaw is fixed in version 2025.12.0 of everest-core. The CVSS 4.0 vector indicates a low severity score of 2.4, reflecting the limited attack surface and impact. No public exploits are known at this time, and the vulnerability was published on January 21, 2026.

Potential Impact

For European organizations, the primary impact of CVE-2025-68132 is the potential for denial of service (DoS) on EV charging infrastructure components that utilize the affected EVerest everest-core versions. This could disrupt EV charging services, leading to operational downtime and customer dissatisfaction. Although the vulnerability does not allow for code execution or data compromise, repeated crashes could degrade system reliability and availability. Organizations operating public or private EV charging networks, especially those with high volumes of serial communication to powermeters, may experience service interruptions. Given the increasing adoption of EVs across Europe, any disruption in charging infrastructure could have cascading effects on transportation and energy management. However, the low CVSS score and requirement for direct serial input control limit the scope and ease of exploitation, reducing the overall risk. Still, critical infrastructure operators should consider this vulnerability in their risk assessments due to the strategic importance of EV charging networks in the European green energy transition.

Mitigation Recommendations

The primary mitigation is to upgrade the EVerest everest-core software to version 2025.12.0 or later, where the vulnerability is fixed. Until patching is possible, organizations should implement strict input validation and filtering on the serial communication channels to prevent malformed SLIP frames from reaching the is_message_crc_correct function. Network segmentation and access controls should be enforced to restrict physical and logical access to the serial interfaces, limiting attacker capability to inject malicious frames. Monitoring and alerting on process crashes or abnormal behavior in the EV charging software can provide early detection of exploitation attempts. Additionally, conducting regular audits of EV charging system firmware and software versions will help ensure timely application of security updates. Vendors and operators should collaborate to establish secure update mechanisms and verify the integrity of software components to prevent tampering.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-15T18:05:52.211Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 697120104623b1157ce4b457

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

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

Last updated: 1/21/2026, 11:52:11 PM

Views: 9

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