CVE-2026-46538
Microsoft UFO Constellation Task-Result Injection
Publication date: 2026-05-27
Last updated on: 2026-05-27
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| microsoft | ufo | From 3.0.1 (inc) to 4-ge2626659 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-345 | The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. |
| CWE-294 | A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Microsoft UFO open-source framework for intelligent automation. Specifically, in version 3.0.1-4-ge2626659, the constellation client tracks pending task responses by session_id only and does not verify that a TASK_END message actually comes from the device that originally received the task.
When a task is sent to a target device, the system records a pending task under a session key and stores the expected device ID. However, when the task is completed, the system ignores the device ID binding and accepts a TASK_END message from any authenticated peer device with the same session_id.
This allows an attacker controlling another authenticated device to send a forged TASK_END message with the same session_id, causing the system to accept the attacker's result data as if it came from the original device. This is an authenticated cross-device task-result injection vulnerability.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker with access to an authenticated device to inject false task completion results into the system.
Because the system accepts forged TASK_END messages from other devices, an attacker can manipulate task outcomes, potentially causing incorrect automation behavior or data corruption.
The CVSS score indicates a moderate severity with a base score of 5.9, highlighting that while the attack requires some privileges, it can lead to integrity loss and partial availability impact.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows an authenticated attacker to inject forged task completion results from a different device, potentially leading to integrity issues in task processing.
While the CVE description does not explicitly mention compliance impacts, the integrity compromise could affect regulatory requirements related to data integrity and system reliability under standards such as GDPR and HIPAA.
However, since there is no direct information provided about compliance implications or data exposure, the exact effect on compliance with GDPR, HIPAA, or similar regulations cannot be determined from the given information.