Skip to content
major vulnerability· requires attention

Unauthenticated OCPP WebSocket access enables impersonation/control of chargers across networks; potential widespread disruption of charging infrastructure.

IoT

CVE-2026-25851

9.4
Critical
EPSS 0.64%Feb 27, 2026

Unauthenticated OCPP WebSocket allows charging-station impersonation and control.

common questions

Is CVE-2026-25851 being exploited?

Not confirmed. CVE-2026-25851 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.

How severe is CVE-2026-25851?

CVE-2026-25851 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-25851?

Not known from our data. No patch reference has been recorded for CVE-2026-25851, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-25851 affect?

CVE-2026-25851 affects OCPP WebSocket endpoints, OCPP-enabled charging stations, Charging backend servers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-25851?

Enforce authentication/token-based authorization on OCPP WebSocket endpoints.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OCPP WebSocket endpointsOCPP-enabled charging stationsCharging backend servers
impact

Unauthenticated attacker can impersonate chargers, issue/receive OCPP commands, escalate access, and corrupt backend data.

action required

Immediate action required

affected versions
Chargemap chargemap.com
  • affectedAll versions

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free