# CVE-2026-28230: Missing authorization in steve

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

- **Severity:** Medium 5.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-6x38-4w7h-cwr8

## 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 (Improper Access Control)

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

It affects 1 product.


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

## Is CVE-2026-28230 being exploited?

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

## Other vulnerabilities in steve-community steve

- [CVE-2024-25407](https://insights.sbomify.com/CVE-2024-25407/): Business logic in n/a (high 7.5)
- [CVE-2024-21550](https://insights.sbomify.com/CVE-2024-21550/): Cross-site scripting in SteVe (medium 6.1)
- [CVE-2024-44843](https://insights.sbomify.com/CVE-2024-44843/): Auth bypass in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

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

Affected product: steve-community steve. 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-28230/ (Markdown: https://insights.sbomify.com/CVE-2026-28230/index.md)
```

## Sources

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

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