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 everest |
|
| CPEs | cpe:2.3:o:linuxfoundation:everest:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Linuxfoundation
Linuxfoundation everest |
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 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | EVerest vulnerable to null pointer dereference during DC_ChargeLoopRes document deserialization | |
| Weaknesses | CWE-476 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-22T16:50:38.843Z
Reserved: 2025-12-15T18:15:08.404Z
Link: CVE-2025-68141
Updated: 2026-01-22T15:09:41.519Z
Status : Analyzed
Published: 2026-01-21T20:16:06.523
Modified: 2026-02-06T21:22:03.747
Link: CVE-2025-68141
No data.
OpenCVE Enrichment
Updated: 2026-01-22T10:08:45Z