Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sat, 30 May 2026 23:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Microsoft
Microsoft ufo |
|
| Vendors & Products |
Microsoft
Microsoft ufo |
Thu, 28 May 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 27 May 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Microsoft UFO open-source framework for intelligent automation across devices and platforms. In 3.0.1-4-ge2626659, Microsoft UFO's constellation client tracks pending task responses by session_id only and does not verify that a TASK_END message came from the device that originally received the task. When the constellation sends a task to a target device, it records a pending Future under a session key. The pending task record stores the expected device ID, but the completion path ignores that binding. If another authenticated peer device sends a forged TASK_END with the same session_id, the constellation accepts the response and completes the victim device's pending Future with attacker-controlled result data. This is an authenticated cross-device task-result injection issue. | |
| Title | Microsoft UFO accepts cross-device TASK_END messages by session_id only, allowing peer task-result injection | |
| Weaknesses | CWE-294 CWE-345 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-28T12:38:02.790Z
Reserved: 2026-05-14T20:42:31.368Z
Link: CVE-2026-46538
Updated: 2026-05-28T12:37:40.469Z
Status : Deferred
Published: 2026-05-27T23:16:48.107
Modified: 2026-06-17T10:53:45.653
Link: CVE-2026-46538
No data.
OpenCVE Enrichment
Updated: 2026-05-30T21:19:39Z