# CVE-2026-46414: Microsoft UFO WebSocket role spoofing allows authenticated peer task hijacking

> Authenticated WebSocket clients can spoof privileged roles to hijack tasks on other devices due to insufficient server-side role validation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 2 Jun 2026

## What is CVE-2026-46414?

CVE-2026-46414 is a high-severity authentication bypass vulnerability in microsoft UFO, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Microsoft UFO open-source framework for intelligent automation across devices and platforms. In 3.0.1-4-ge2626659, Microsoft UFO's WebSocket control plane trusts client-supplied identity and role fields in task messages. A client connection can register as a normal device, but later send a TASK message claiming client_type="constellation" and target_id=<victim-device-id>. The server trusts the role and target values from the wire message rather than enforcing the role registered for that WebSocket connection. As a result, any authenticated WebSocket client with the shared server token can spoof the higher-privilege constellation role and dispatch attacker-controlled tasks to another connected device. The same client registry also allows duplicate client_id registration, overwriting an existing live client's stored websocket, role, and task protocol. This is an authenticated WebSocket role/identity spoofing issue leading to peer task hijacking.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-46414?


## How do I fix CVE-2026-46414?

No fix has been published for CVE-2026-46414 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46414 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46414 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46414 and fix it if it is affected.

What it is: CVE-2026-46414 is a high-severity authentication bypass vulnerability in microsoft UFO, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46414 exists.

Affected product: microsoft UFO. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46414/ (Markdown: https://insights.sbomify.com/CVE-2026-46414/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46414
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46414
- OSV: https://osv.dev/vulnerability/CVE-2026-46414

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46414/
Summaries are generated and may contain mistakes; the official description above is the record.