CVE-2026-22552
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWebSocket 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOCPP WebSocket endpoints lack authentication, allowing unauthenticated attackers to connect using a known or discovered charging station identifier and impersonate legitimate chargers. This enables unauthorized command execution and data manipulation in the charging infrastructure backend.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OCPP WebSocket endpoint exposureScan network for open ports running OCPP WebSocket services (typically ports 8080, 8443, or custom WS/WSS ports). Use tools like netstat, nmap, or review firewall rules to determine if WebSocket endpoints are internet-facing or accessible from untrusted networks.Affected if OCPP WebSocket endpoints are accessible without network segmentation or firewall restrictions
-
Verify WebSocket authentication requirementAttempt to establish a WebSocket connection to the OCPP endpoint without providing any credentials or authentication tokens. Observe if the connection is accepted or rejected.Affected if WebSocket connection is accepted without requiring any authentication credentials
-
Test station identifier impersonationSend a WebSocket connection request using a known or guessed charging station identifier (e.g., in the connection URL path or initial message) without providing valid authentication. Monitor if the backend accepts the connection and allows OCPP command exchange.Affected if Connection is established and OCPP commands can be sent using an arbitrary station identifier without validation
-
Confirm backend command validationAfter connecting (with or without valid credentials), attempt to send OCPP commands (such as BootNotification, Heartbeat, or status commands) to verify if the backend executes them without verifying the station's identity or requiring additional authentication.Affected if Backend processes and executes OCPP commands without confirming the requester's identity through authentication
The environment is affected if OCPP WebSocket endpoints are accessible and allow connections without requiring authentication or validating station identifiers before accepting commands.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strong authentication for WebSocket connections (e.g., token-based or TLS client certificate authentication) and validate station identifiers before allowing any OCPP command execution.
- Consultation6.0 h
- Implementation16.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22552 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data