# CVE-2026-24003: EvseV2G has sequence state validation bypass

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

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-9vv5-67cv-9crq

## 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 (Incorrect Authorization), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-24003?

It affects 1 product.


Products: 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.

## Is CVE-2026-24003 being exploited?

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

## Other vulnerabilities in everest-core

- [CVE-2026-22790](https://insights.sbomify.com/CVE-2026-22790/): EVerest's unchecked SLAC payload length causes stack overflow in HomeplugMessage::setup_payload (high 8.8)
- [CVE-2026-22593](https://insights.sbomify.com/CVE-2026-22593/): EVerest has off-by-one stack buffer overflow in IsoMux certificate filename parsing (high 8.4)
- [CVE-2026-23995](https://insights.sbomify.com/CVE-2026-23995/): EVerest has stack buffer overflow in ifreq.ifr_name when interface name exceeds IFNAMSIZ (high 8.4)
- [CVE-2025-68137](https://insights.sbomify.com/CVE-2025-68137/): EVerest's Integer Overflow and Signed to Unsigned conversion lead to either stack buffer overflow or infinite loop (high 8.4)
- [CVE-2026-33009](https://insights.sbomify.com/CVE-2026-33009/): EVerest: MQTT Switch-Phases Command Data Race Causing Charger State Corruptio (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24003 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-24003 in the wild and no public exploit code.

Affected product: everest-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24003/ (Markdown: https://insights.sbomify.com/CVE-2026-24003/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24003
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24003
- OSV: https://osv.dev/vulnerability/CVE-2026-24003

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24003/
Summaries are generated and may contain mistakes; the official description above is the record.