CVE-2026-33014 EVerest has Delayed Authorization Response Bypasses Termination After RemoteStop
Attackers can keep EV charging transactions open after remote stop commands by exploiting delayed authorization responses, requiring a software patch.
- 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-2026-33014?
CVE-2026-33014 is a medium-severity vulnerability in everest-core, published on 26 Mar 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. Prior to version 2026.02.0, during RemoteStop processing, a delayed authorization response restores `authorized` back to true, defeating the `stop_transaction()` call condition on PowerOff events. As a result, the transaction can remain open even after a remote stop. Version 2026.02.0 contains a patch.
Weakness: CWE-863
Which versions are affected by CVE-2026-33014?
It affects 1 product.
Products include Linuxfoundation Everest.
How do I fix CVE-2026-33014?
No fix has been published for CVE-2026-33014 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-33014 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33014 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-43xm-5m3v-52hm.