Service interruption via unreleased websocket allocations
Published Jan 21, 2026 · Updated Jan 21, 2026
Resource exhaustion in EVerest Core with libocpp before 0.30.1 allows remote attackers to interrupt charging services. WebsocketLibwebsockets::thread_websocket_client_loop repeatedly duplicates the CSMS hostname, charge-point path, and protocol string without freeing the heap allocations. Reachability requires failed or frequent OCPP reconnects from an adjacent network position; sustained attempts exhaust memory and stop the charging software.
Summary
What happened
Resource exhaustion in EVerest Core with libocpp before 0.30.1 allows remote attackers to interrupt charging services. WebsocketLibwebsockets::thread_websocket_client_loop repeatedly duplicates the CSMS hostname, charge-point path, and protocol string without freeing the heap allocations. Reachability requires failed or frequent OCPP reconnects from an adjacent network position; sustained attempts exhaust memory and stop the charging software.
The record
- CVE
- CVE-2025-68138
- Published
- Jan 21, 2026
- Updated
- Jan 21, 2026
- Vendor
- EVerest
- Product
- EVerest Core
- Classifications
- CWE-770, T1499.003
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2026CVE publishedPublication date reported by the CVE source.
- Jan 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=libocpp < 0.30.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo