EVerest everest-core
EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2025.10.0
Fixed in 2025.10.0
Mitigation
Upgrade everest-core to 2025.10.0 or later.
References
- Vendor advisory github.com/EVerest/everest-core/security/advis…
Timeline
Days relative to CVE publicationFirst public PoC 223 days after publication; not in CISA KEV. First PoC: EVerest 2025.9.0 - DoS (Exploit-DB, 2 Sep 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| Exploit-DB | EVerest 2025.9.0 - DoS | 2 Sep 2026 | 14 Nov 2026 |