CVE-2026-54568: Microsoft UFO authorization bypass in WebSocket handler

CVE-2026-54568 · Severity: medium · CVSS 4.3 · Published 2026-07-16

Microsoft UFO is an open-source framework used for automating tasks across different devices and platforms. A security flaw in the framework's communication server allows a connected device to request and receive sensitive system information from other devices on the same network. This could allow an attacker to gather technical details like hostnames, internal IP addresses, and operating system versions, which are often used to plan further attacks.

Technologies: Microsoft UFO. Vendors: Microsoft.

Quick answers

Is CVE-2026-54568 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54568 being exploited in the wild.
How severe is CVE-2026-54568?
Medium severity, with a CVSS score of 4.3, published 16 July 2026.
Which products and versions are affected?
Microsoft UFO >= 3.0.0, < 3.0.6.
Is there a fix for CVE-2026-54568?
A patch was published on 2026-06-06: Fix committed to main branch and version 3.0.6 released. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54568 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-54568?
Check whether you run Microsoft UFO at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A missing authorization check in the Microsoft UFO WebSocket server allows an authenticated client with the 'DEVICE' role to perform actions intended only for 'constellation' (orchestrator) roles. Specifically, the 'DEVICE_INFO_REQUEST' handler in 'ufo/server/ws/handler.py' fails to validate if the requester has the appropriate permissions to access metadata for a specific 'target_id'. An attacker who knows a victim's device ID can retrieve that device's 'system_info', including hostnames, internal IPs, OS versions, and custom metadata. The vulnerability stems from a lack of both function-level and object-level authorization checks in 'handle_device_info_request' and 'get_device_info'. This issue is resolved in version 3.0.6.

Affected products

  • Microsoft UFO >= 3.0.0, < 3.0.6

Timeline

  • 2026-06-06: patched: Fix committed to main branch and version 3.0.6 released.
  • 2026-07-16: disclosed: Advisory published by GitHub and NVD.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.