High severity · published Jan 21, 2026
CVE-2025-68137
EVerest is an EV charging software stack
8.3
CVSS
1.3%
EPSS
No
On KEV
Description
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 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.
CVSS vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Attack vector
Adjacent
Complexity
High
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)1.3% · higher than 70% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EV
Everest · Linuxfoundation
before 2025.10.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-68137
CVE.org
https://www.cve.org/CVERecord?id=CVE-2025-68137
Exploit
https://github.com/EVerest/everest-core/security/advisories/GHSA-7qq4-q9r8-wc7w
More from Everest
9.1
CVE-2026-27816
EVerest's ISO15118 update_energy_transfer_modes overflow can corrupt EVSE state
9.1
CVE-2026-27815
EVerest: ISO15118 session_setup payment options overflow can corrupt EVSE state
8.8
CVE-2026-22790
EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload
7.8
CVE-2026-23995
EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ
7.8
CVE-2026-22593
EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing
