Skip to content
Fencer Vulns
high 8.4

CVE-2025-68137 json

EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop

published 2026-01-21 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-206317

cvss
8.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • linuxfoundation everest 2025.10.0

Timeline

  1. Published
  2. First public exploit (EDB-52679)

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
9 mo ago

Exploit prediction

1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-52679 EVerest 2025.9.0 - DoS dos, 2026-09-02
  • github.com https://github.com/EVerest/everest-core/security/advisories/GHSA-7qq4-q9r8-wc7w referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.4 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

  • EVerest everest-core

Classification

Weakness
  • CWE-120 Buffer Copy without Checking Size of Input
  • CWE-835 Loop with Unreachable Exit Condition

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.