CVE-2026-28230 Missing authorization in steve

Medium 5.7 Published Updated

Attackers can terminate other chargers' active sessions by sending StopTransaction messages without ownership verification, disrupting EV charging operations.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-28230?

CVE-2026-28230 is a medium-severity missing authorization vulnerability in steve-community steve, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

SteVe is an open-source EV charging station management system. In versions up to and including 3.11.0, when a charger sends a StopTransaction message, SteVe looks up the transaction solely by transactionId (a sequential integer starting from 1) without verifying that the requesting charger matches the charger that originally started the transaction. Any authenticated charger can terminate any other charger’s active session across the entire network. The root cause is in OcppServerRepositoryImpl.getTransaction() which queries only by transactionId with no chargeBoxId ownership check. The validator checks that the transaction exists and is not already stopped but never verifies identity. As an attacker controlling a single registered charger I could enumerate sequential transaction IDs and send StopTransaction messages targeting active sessions on every other charger on the network simultaneously. Combined with FINDING-014 (unauthenticated SOAP endpoints), no registered charger is even required — the attack is executable with a single curl command requiring only a known chargeBoxId. Commit 7f169c6c5b36a9c458ec41ce8af581972e5c724e contains a fix for the issue.

Weakness: CWE-284

Which versions are affected by CVE-2026-28230?

It affects 1 product.

Products include Steve-Community Steve.

How do I fix CVE-2026-28230?

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

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-28230 being exploited?

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

Sources

Also known as GHSA-6x38-4w7h-cwr8.

Is CVE-2026-28230 in your software?

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

Check your SBOMs for free