Unauthenticated station impersonation via unverified WebSocket identifiers
Published Feb 26, 2026 · Updated Feb 26, 2026
Missing authentication in CloudCharge in all versions allows remote attackers to impersonate charging stations through OCPP WebSockets. The endpoint accepts a known or discovered charging station identifier without authenticating the connection, then permits OCPP commands to be sent or received as that charger. Possession or discovery of an identifier is sufficient to manipulate backend data and obtain unauthorized control of charging infrastructure.
Summary
What happened
Missing authentication in CloudCharge in all versions allows remote attackers to impersonate charging stations through OCPP WebSockets. The endpoint accepts a known or discovered charging station identifier without authenticating the connection, then permits OCPP commands to be sent or received as that charger. Possession or discovery of an identifier is sufficient to manipulate backend data and obtain unauthorized control of charging infrastructure.
The record
- CVE
- CVE-2026-20781
- Published
- Feb 26, 2026
- Updated
- Feb 26, 2026
- Vendor
- CloudCharge AB
- Product
- CloudCharge
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2026CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo