CVE-2025-68133 EVerest's unlimited connections can lead to DoS through operating system resource exhaustion
Attackers can cause denial of service in EVerest EV charging software by exhausting system resources through unlimited TCP connections.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-68133?
CVE-2025-68133 is a high-severity denial of service vulnerability in everest-core, published on 21 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
EVerest is an EV charging software stack. In versions 2025.9.0 and below, an attacker can exhaust the operating system's memory and cause the module to terminate by initiating an unlimited number of TCP connections that never proceed to ISO 15118-2 communication. This is possible because a new thread is started for each incoming plain TCP or TLS socket connection before any verification occurs, and the verification performed is too permissive. The EVerest processes and all its modules shut down, affecting all EVSE functionality. This issue is fixed in version 2025.10.0.
Weakness: CWE-770
Which versions are affected by CVE-2025-68133?
It affects 1 product.
Products include Linuxfoundation Everest.
How do I fix CVE-2025-68133?
No fix has been published for CVE-2025-68133 yet. Limit exposure of the affected software until one is available.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2025-68133 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68133 exists.
Other vulnerabilities in everest-core
- CVE-2026-22790 EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload
- CVE-2026-22593 EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing
- CVE-2026-23995 EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ
- CVE-2025-68137 EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop
- CVE-2026-33009 EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio
Sources
Also known as GHSA-mv3w-pp85-5h7c.