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

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

- **Severity:** Low 2.4 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2026
- **Updated:** 21 Jan 2026
- **Also known as:** GHSA-79gc-m8w6-9hx5

## 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 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-68132?

It affects 1 product.


Products: 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.

## Is CVE-2025-68132 being exploited?

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

## Other vulnerabilities in everest-core

- [CVE-2026-22790](https://insights.sbomify.com/CVE-2026-22790/): EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload (high 8.8)
- [CVE-2026-22593](https://insights.sbomify.com/CVE-2026-22593/): EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing (high 8.4)
- [CVE-2026-23995](https://insights.sbomify.com/CVE-2026-23995/): EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ (high 8.4)
- [CVE-2025-68137](https://insights.sbomify.com/CVE-2025-68137/): EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop (high 8.4)
- [CVE-2026-33009](https://insights.sbomify.com/CVE-2026-33009/): EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68132 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68132 exists.

Affected product: everest-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68132/ (Markdown: https://insights.sbomify.com/CVE-2025-68132/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68132
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68132
- OSV: https://osv.dev/vulnerability/CVE-2025-68132

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68132/
Summaries are generated and may contain mistakes; the official description above is the record.