CVE-2025-68132 EVerest has out-of-bounds read in DZG_GSH01 SLIP CRC parser that can crash powermeter driver

Low 2.4 Published Updated

An attacker controlling serial input can crash the EVerest powermeter driver via an out-of-bounds read in the SLIP CRC parser.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-68132?

CVE-2025-68132 is a low-severity denial of service vulnerability in everest-core, published on 21 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-125

Which versions are affected by CVE-2025-68132?

It affects 1 product.

Products include Linuxfoundation Everest.

How do I fix CVE-2025-68132?

No fix has been published for CVE-2025-68132 yet. Limit exposure of the affected software until one is available.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2025-68132 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68132 exists.

Sources

Also known as GHSA-79gc-m8w6-9hx5.

Is CVE-2025-68132 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free