CVE-2026-46414: Microsoft UFO WebSocket Authentication Bypass and Role Spoofing

Technical summary

The vulnerability stems from two related design flaws in UFO's WebSocket control plane. First, the server validates the shared server token but fails to enforce consistency between the role registered at connection time and the client_type/role claims in subsequent TASK messages. An authenticated client can send wire messages declaring client_type="constellation" and specifying an arbitrary target_id, and the server accepts these claims without verifying they match the connection's initial authorization state. Second, the client registry does not enforce uniqueness on client_id, permitting duplicate registrations that overwrite existing WebSocket connections. A malicious actor can register with a victim device's client_id to steal or terminate that device's active session. Both flaws require prior authentication (shared server token), but once inside, an attacker gains lateral movement and task injection capabilities across the peer network.

Business impact

Organizations deploying UFO for distributed automation face significant operational and security risks. A compromised or malicious insider with valid credentials can hijack automation workflows targeting critical infrastructure, manufacturing lines, or enterprise systems. Tasks injected via spoofed constellation identity could exfiltrate data, modify configuration, execute arbitrary code, or disrupt services on target devices. The ability to overwrite legitimate client registrations also enables denial-of-service attacks by forcing disconnection of authorized devices. In supply-chain scenarios where UFO orchestrates cross-platform operations, such attacks could propagate widely before detection.

Affected systems

Microsoft UFO version 3.0.1-4-ge2626659 is confirmed vulnerable. Because the source data does not list specific vendor products and this is an open-source framework, deployments worldwide may be affected. Organizations should audit all instances of UFO running version 3.0.1-4-ge2626659 or earlier. Check deployment documentation and version control logs to identify all systems, especially those handling sensitive automation tasks or operating in zero-trust environments where peer compromise was not anticipated.

Exploitability

Exploitation requires prior authentication—an attacker must possess or obtain a valid shared server token to connect to the WebSocket control plane. This prerequisite significantly reduces the attack surface for internet-facing deployments but does not eliminate risk in scenarios where tokens are widely distributed, reused, or insufficiently rotated. Once authenticated, the exploit is trivial: send a TASK message with spoofed role and target fields. No interaction with the user of the target device is required, and the attack is not detected by default. The ability to overwrite client registrations and redirect live sessions further lowers the bar for causing impact. In insider threat or compromised-credential scenarios, this is a high-confidence attack path.

Remediation

Upgrade to a patched version of Microsoft UFO that enforces role consistency and prevents duplicate client registration. Verify the exact patched version against the official Microsoft advisory. Until a patch is available, implement network controls: restrict WebSocket access to trusted subnets, enforce certificate-based mutual TLS authentication in addition to token sharing, implement rate limiting on TASK message dispatch, and monitor for anomalous role transitions or duplicate client_id registrations. Rotate shared server tokens on a strict schedule and audit token distribution to reduce the likelihood of credential compromise.

Patch guidance

Consult the official Microsoft security advisory for CVE-2026-46414 to identify the recommended patched version. Apply patches in a staged approach: test in a non-production UFO environment first to ensure automation workflows continue to function, then roll out to production instances, starting with those handling the most sensitive operations. Given the ease of exploitation post-authentication, prioritize patching higher than routine updates. Maintain inventory of all UFO deployments so no instance is missed.

Detection guidance

Monitor WebSocket control plane logs for: (1) TASK messages where the claimed client_type or role differs from the registered role for that connection session, (2) multiple WebSocket connections registering the same client_id in short succession, (3) TASK messages targeting devices not expected to communicate, and (4) rapid role transitions or high-volume task dispatch from a single authenticated client. Implement alerting on these patterns. Log all connection registrations, role assignments, and task dispatches with timestamps and source identity for forensic analysis. If UFO does not natively emit these logs, consider deploying a proxy or network TAP to capture WebSocket traffic for post-incident investigation.

Why prioritize this

This vulnerability scores CVSS 8.8 (HIGH) and warrants immediate attention despite not yet appearing on the CISA KEV catalog. The combination of high privileges gained post-authentication, ease of exploitation, and direct impact on mission-critical automation systems makes it a priority for any organization using UFO. The lack of KEV status does not imply low risk—it indicates the advisory is recent or exploitation is not yet widespread in public reporting. Do not delay patching or hardening based on KEV absence.

Risk score, explained

The CVSS 3.1 score of 8.8 reflects high severity across confidentiality, integrity, and availability. Attack vector is network (AV:N), attack complexity is low (AC:L), and privileges required is low (PR:L)—authenticated users can easily exploit this without special conditions. User interaction is not required (UI:N), and the scope is unchanged (S:U). The impact is complete: an attacker gains high-confidence capability to read task data, modify device state, and disrupt operations. The primary limiting factor is the authentication requirement (PR:L), which prevents unauthenticated network attack but is often insufficient as a control in environments with credential leakage, insider threats, or token reuse.

Frequently asked questions