Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 06 Feb 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linuxfoundation
Linuxfoundation libocpp |
|
| CPEs | cpe:2.3:a:linuxfoundation:libocpp:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Linuxfoundation
Linuxfoundation libocpp |
Fri, 23 Jan 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Everest
Everest everest-core |
|
| Vendors & Products |
Everest
Everest everest-core |
Thu, 22 Jan 2026 23:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 21 Jan 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | EVerest affected by memory exhaustion in libocpp | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-22T21:56:29.394Z
Reserved: 2025-12-15T18:09:12.695Z
Link: CVE-2025-68138
Updated: 2026-01-22T21:56:24.054Z
Status : Analyzed
Published: 2026-01-21T20:16:06.007
Modified: 2026-02-06T21:22:15.583
Link: CVE-2025-68138
No data.
OpenCVE Enrichment
Updated: 2026-01-22T10:08:31Z