CVE-2026-28230

MEDIUMNVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.3 under NVD CVSS v3. EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-8917 (ENISA EUVD)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 26, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Any authenticated charger can terminate any other charger’s active transaction (missing ownership verification on StopTransaction) · Advisory · steve-community/steve · GitHub

https://github.com/steve-community/steve/security/advisories/GHSA-6x38-4w7h-cwr8
GitHub commit Patch Available

commit 7f169c6c5b36 (steve-community/steve)

Patch available: steve-community/steve steve-3.12.0 (contains commit 7f169c6c5b36)

https://github.com/steve-community/steve/commit/7f169c6c5b36a9c458ec41ce8af581972e5c724e

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 218 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-30 23:55 UTCOSV refresh
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-25 14:38 UTCEG score recompute
  10. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-23 04:01 UTCEG score recompute
  13. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-18 03:50 UTCEG score recompute
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-12 16:16 UTCEG score recompute
Show 71 more
  1. 2026-10-11 19:59 UTCEG score recompute
  2. 2026-10-11 17:12 UTCEG score recompute
  3. 2026-10-11 14:43 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-08 13:24 UTCOSV refresh
  9. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-18 19:06 UTCOSV refresh
  22. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  27. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-08-30 22:17 UTCOSV refresh
  37. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  42. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  52. 2026-08-14 08:52 UTCEG score recompute
  53. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  54. 2026-08-13 00:51 UTCEG score recompute
  55. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  56. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  57. 2026-08-11 08:42 UTCEG score recompute
  58. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  59. 2026-08-10 08:34 UTCEG score recompute
  60. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-08-09 08:32 UTCEG score recompute
  62. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  63. 2026-08-07 20:34 UTCEG score recompute
  64. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  65. 2026-08-06 02:56 UTCEG score recompute
  66. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  67. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  68. 2026-08-04 04:56 UTCEG score recompute
  69. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  70. 2026-08-02 19:26 UTCEG score recompute
  71. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-28230?
CVE-2026-28230 is a medium-severity vulnerability; its CVE record was published on February 26, 2026. 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…
When was the CVE record for CVE-2026-28230 published?
The CVE record for CVE-2026-28230 was published on February 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-28230 actively exploited?
CVE-2026-28230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-28230?
CVE-2026-28230 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-28230?
A fix for CVE-2026-28230 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-28230

Explore →

Is Your Infrastructure Affected by CVE-2026-28230?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs