/

CVE-2026-20744

Severity:

CRITICAL RISK

(9.8)

Authentication Bypass (CWE-284) in EV Charging WebSocket

CVE-2026-20744

Deferred

Vulnerability type

Category:

Authentication and Authorization Bypass

CWE:

CWE-284

Impact:

Privilege Escalation and Unauthorized Control

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The EV charging station's WebSocket endpoint accepts connections without enforcing proper authentication or authorization checks.

Under these conditions, an attacker connecting to the endpoint may escalate privileges, gaining access to control or management capabilities of charging infrastructure.

Affected context

This vulnerability arises in network-connected EV charging stations that expose a WebSocket endpoint for status, control, or management functions.

It is relevant when the endpoint is reachable over local network, corporate LAN, or public internet and does not reliably verify client identity or enforce access controls.

The risk increases in deployments where the WebSocket is used for sensitive operations such as starting or stopping charging sessions, configuring station parameters, or updating firmware.

Exploit preconditions

  • Attack surface: Network-accessible WebSocket endpoint on the charging station or its backend.
  • Required access: Ability to establish a WebSocket connection from a reachable network segment (e.g., same Wi‑Fi, corporate network, or internet if exposed).
  • Trigger point: Initiation of a WebSocket session where the server fails to enforce authentication or authorization for incoming connections and subsequent messages.
  • Why exploitation is possible: Insufficient access control (CWE-284) allows unauthenticated or improperly authenticated clients to perform actions reserved for trusted or privileged users.

Why this happens

The underlying issue is a missing or incomplete enforcement of access control on a sensitive communication channel, mapped to CWE-284: Improper Access Control.

The WebSocket endpoint treats incoming connections as trusted without requiring strong authentication tokens, session validation, or role-based authorization checks.

As a result, operations exposed over this channel—such as control commands or configuration changes—can be invoked by any client that can connect, violating the principle of least privilege and secure default access.

Potential impact

  • An attacker may gain unauthorized control over individual charging sessions (start, stop, or modify charging).
  • An attacker could change configuration settings on charging stations, potentially degrading safety or reliability.
  • Unauthorized users may access operational data or telemetry from charging infrastructure.
  • Malicious actors could disrupt service availability by issuing control commands to multiple stations.
  • In some deployments, attackers can leverage the station as a pivot point to move laterally within the connected network.

General mitigation guidance

Mitigation typically focuses on enforcing robust access control for all stateful communication channels, including WebSockets.

Common defensive patterns include:

  • Requiring strong, verifiable authentication for every WebSocket connection, such as short-lived tokens tied to user or device identity.
  • Applying fine-grained authorization checks on each action or message, aligned with clearly defined roles and permissions.
  • Designing endpoints with secure-by-default behavior, where unauthenticated connections have no access to sensitive operations or data.
  • Isolating control channels from public networks and restricting access through network segmentation and gateway controls.
  • Implementing least-privilege principles for both clients and backend services to minimize the blast radius of any compromise.

How teams detect issues like this

Detection efforts can focus on both code-level and operational signals:

  • Static analysis and manual code review to identify WebSocket handlers or controllers that lack explicit authentication and authorization checks.
  • Verification that all control paths from WebSocket messages pass through a centralized access-control layer or middleware.
  • Security testing and red-teaming exercises that attempt unauthenticated WebSocket connections and privileged actions, ensuring they are rejected.
  • Logging and monitoring of WebSocket connection patterns to spot anomalous or unauthorized usage, correlating with identity and access policies.
  • Policy enforcement within CI/CD pipelines that require security review for new or modified network-exposed endpoints.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-188-01.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-188-01
hydroquebec.comhydroquebec.com/nous-joindre/

Frequently asked

questions

It can be, depending on deployment. If the WebSocket endpoint is exposed beyond a tightly controlled local network, attackers may connect remotely and exploit the missing access controls.

An attacker generally needs only network-level access to reach the WebSocket endpoint. No valid credentials are required if authentication is not enforced or is trivially bypassed.

Implement strict authentication and authorization for all WebSocket connections, routing every privileged operation through a centralized access-control mechanism and denying unauthenticated or unauthorized requests by default.

Treat every network-exposed endpoint as untrusted, require identity verification before granting any capabilities, enforce least privilege on operations, and integrate security reviews and automated checks into development workflows for new communication channels.

Find out what's already
exploitable in your codebase.