CVE-2026-27772
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 known charging station identifiers and impersonate legitimate chargers. This enables issuance and reception of OCPP commands without proper validation, leading to privilege escalation and unauthorized control of charging infrastructure.
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 exposed OCPP WebSocket endpointsScan network for open ports typically used by OCPP (TCP 8080, 8081, 8443, 9000) or review reverse proxy/web server logs for websocket upgrade requests to OCPP paths such as /ocpp, /ws, /websocket/ocppAffected if OCPP WebSocket endpoints are reachable from untrusted networks without prior authentication requirements
-
Verify station identifier validation is enforcedReview application code or configuration for validation logic that checks charging station identifiers (chargePointId) against a trusted registry or approved list before accepting WebSocket connectionsAffected if Station identifiers are accepted without verification against a trusted source or database of authorized chargers
-
Confirm authentication is required for WebSocket handshakeInspect the WebSocket handshake process or middleware to determine if authentication tokens, certificates, or credentials are validated before the connection is establishedAffected if WebSocket connections to OCPP endpoints complete without requiring any form of authentication token or credential validation
-
Test unauthorized command issuance capabilityUsing a WebSocket client, attempt to connect using a known or guessed station identifier and send OCPP messages (e.g., BootNotification, Heartbeat) without providing valid credentialsAffected if Connections succeed and OCPP commands are processed using arbitrary station identifiers without rejection or credential challenge
-
Review OCPP connection configurationExamine configuration files, environment variables, or API gateway settings related to OCPP WebSocket handling to identify if authentication enforcement is disabled or missingAffected if Configuration shows authentication is disabled, optional, or not defined for OCPP WebSocket endpoints
A user is affected if OCPP WebSocket endpoints accept connections without requiring valid authentication and without validating station identifiers against a trusted registry.
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 robust authentication for all WebSocket connections, including station credential verification, token-based or certificate-based authentication, and validation of station identifiers against a trusted registry before allowing command execution.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27772 — 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-27772 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