CVE-2026-28230: In SteVe, any authenticated charger can terminate any other charger's active transaction (missing ownership verification on StopTransaction)

Published Feb 26, 2026
·
Updated

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.

Affected Software

2 affected components
SteVe SteVe<=3.11.0
Steve-community Steve<=3.11.0

Event History

Feb 26, 2026
CVE Published
via MITRE·10:49 PM
Data Sourced
via MITRE·10:49 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 23, 58145
Event
via FIRST·10:39 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-28230?

CVE-2026-28230 is considered a critical vulnerability due to the lack of ownership verification allowing one authenticated charger to terminate another charger's transaction.

2

How do I fix CVE-2026-28230?

To fix CVE-2026-28230, upgrade SteVe to version 3.11.1 or later, which includes the necessary ownership verification for StopTransaction messages.

3

Who is affected by CVE-2026-28230?

Any users operating SteVe versions up to and including 3.11.0 are affected by CVE-2026-28230.

4

What type of attack does CVE-2026-28230 enable?

CVE-2026-28230 enables unauthorized transaction termination attacks by authenticated chargers on the SteVe platform.

5

Are there any known exploits for CVE-2026-28230?

There are no known public exploits for CVE-2026-28230, but the vulnerability poses a significant risk due to its potential exploitation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203