EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 8.4epss 1.3%
from disclosure to weapon224 days
Published on NVDJan 21
1st PoC+224d
exploitation probability
1.3%top 31% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
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:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Affected products
EVerest · everest-corepublic PoCs found — 1
exploitdbwww.exploit-db.com/exploits/52679unverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.