# CVE-2026-54568: Microsoft UFO: Missing Authorization in DEVICE_INFO_REQUEST Allows a DEVICE Client to Read Another Device's system_info

> A device client can read another device's system information by bypassing authorization checks in the WebSocket handler.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-hc27-j4p9-qm2x

## What is CVE-2026-54568?

CVE-2026-54568 is a medium-severity missing authorization vulnerability in microsoft UFO, published on 16 Jul 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. From 3.0.0 until 3.0.6, a client connected to the UFO WebSocket server as a DEVICE could call DEVICE_INFO_REQUEST with another device's target_id and receive that device's server-side system_info through ufo/server/ws/handler.py, because handle_device_info_request and get_device_info did not enforce the constellation-only role or object-level authorization boundary. This issue is fixed in version 3.0.6.

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

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


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

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

## Is CVE-2026-54568 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54568 is a medium-severity missing authorization vulnerability in microsoft UFO, published on 16 Jul 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-54568 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-54568/ (Markdown: https://insights.sbomify.com/CVE-2026-54568/index.md)
```

## Sources

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

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