CVE-2026-27028
Awaiting Analysis Awaiting Analysis - Queue
Unauthenticated WebSocket Access Enables OCPP Station Impersonation

Publication date: 2026-02-27

Last updated on: 2026-03-05

Assigner: ICS-CERT

Description
WebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging infrastructure, and corruption of charging network data reported to the backend.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-27
Last Modified
2026-03-05
Generated
2026-05-07
AI Q&A
2026-02-27
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
mobility46 mobility46.se *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs because WebSocket endpoints used by charging stations lack proper authentication mechanisms. This allows attackers to connect to the OCPP WebSocket endpoint without needing to authenticate themselves.

An attacker can impersonate a legitimate charging station by using a known or discovered charging station identifier. Once connected, the attacker can issue or receive OCPP commands as if they were the legitimate charger.


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized control over charging infrastructure, allowing attackers to escalate privileges and manipulate the charging network.

Attackers can corrupt data reported to the backend, potentially causing operational disruptions or incorrect billing information.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart