CVE-2026-24003 EvseV2G has sequence state validation bypass

Medium 4.3 Published Updated

Attackers can bypass authentication and state validation in EVerest EV charging software to send illegitimate requests and prepare charging contexts.

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-24003?

CVE-2026-24003 is a medium-severity authentication bypass vulnerability in everest-core, published on 26 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 up to and including 2025.12.1, it is possible to bypass the sequence state verification including authentication, and send requests that transition to forbidden states relative to the current one, thereby updating the current context with illegitimate data.cThanks to the modular design of EVerest, authorization is handled in a separate module and EVSEManager Charger internal state machine cannot transition out of the `WaitingForAuthentication` state through ISO 15118-2 communication. From this state, it was however possible through ISO 15118-2 messages which are published to the MQTT server to trick it into preparing to charge, and even to prepare to send current. The final requirement to actually send current to the EV was the closure of the contactors, which does not appear to be possible without leaving the `WaitingForAuthentication` state and leveraging ISO 15118-2 messages. As of time of publication, no fixed versions are available.

Weakness: CWE-863, CWE-287

Which versions are affected by CVE-2026-24003?

It affects 1 product.

Products include Linuxfoundation Everest.

How do I fix CVE-2026-24003?

No fix has been published for CVE-2026-24003 yet. Limit exposure of the affected software until one is available.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-24003 being exploited?

There is no known exploitation of CVE-2026-24003 in the wild and no public exploit code.

Sources

Also known as GHSA-9vv5-67cv-9crq.

Is CVE-2026-24003 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free