CVE-2025-68137
Published: 21 January 2026
Summary
CVE-2025-68137 is a high-severity Classic Buffer Overflow (CWE-120) vulnerability in Linuxfoundation Everest. Its CVSS base score is 8.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 16.2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).
Deeper analysis
CVE-2025-68137 is an integer overflow vulnerability in EVerest, an open-source EV charging software stack. Prior to version 2025.10.0, the issue occurs in the `SdpPacket::parse_header()` function, where a complete header of size 8 is read but the current buffer length is erroneously set to 7. This causes the remaining length calculation—current length minus header length—to yield a negative value, which is interpreted as `SIZE_MAX` (or slightly less) when cast to the expected `size_t` type.
Attackers on an adjacent network (AV:A) with no privileges (PR:N) and no user interaction (UI:N) can exploit this vulnerability, though it requires high attack complexity (AC:H). Depending on server configuration—plain TCP or TLS—exploitation leads to either an infinite loop or a stack buffer overflow. The vulnerability has a CVSS v3.1 base score of 8.3 (AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) and is linked to CWE-120 (buffer copy without checking size of input) and CWE-835 (infinite loop).
EVerest version 2025.10.0 addresses the vulnerability. Additional details on the issue and remediation are available in the GitHub security advisory at https://github.com/EVerest/everest-core/security/advisories/GHSA-7qq4-q9r8-wc7w.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-206317
Vulnerability details
EVerest is an EV charging software stack. Prior to version 2025.10.0, an integer overflow occurring in `SdpPacket::parse_header()` allows the current buffer length to be set to 7 after a complete header of size 8 has been read. The remaining length…
more
to read is computed using the current length subtracted by the header length which results in a negative value. This value is then interpreted as `SIZE_MAX` (or slightly less) because the expected type of the argument is `size_t`. Depending on whether the server is plain TCP or TLS, this leads to either an infinite loop or a stack buffer overflow. Version 2025.10.0 fixes the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Integer overflow in network packet parser enables remote exploitation of stack buffer overflow or infinite loop on adjacent network service.
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Timely flaw remediation ensures deployment of the fixed EVerest version 2025.10.0, directly eliminating the integer overflow vulnerability.
Information input validation enforces checks on SDP packet header lengths and buffer sizes, preventing integer overflows from malformed inputs.
Memory protection mechanisms like stack canaries or DEP mitigate exploitation of the resulting stack buffer overflow.