Quick answers
- Is CVE-2026-46414 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46414 being exploited in the wild.
- How severe is CVE-2026-46414?
- High severity, with a CVSS score of 8.8, published 27 May 2026.
- Which products and versions are affected?
- Microsoft UFO 3.0.1-4-ge2626659.
- Is there a fix for CVE-2026-46414?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-46414 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-46414?
- 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
The vulnerability exists in the WebSocket control plane of Microsoft UFO (specifically within `ufo/server/ws/handler.py`). The server fails to enforce the role and identity established during the initial connection registration, instead trusting 'client_type' and 'target_id' fields provided in subsequent TASK messages. An attacker with a valid server token can register as a standard device and then send messages claiming the 'constellation' role to dispatch tasks to any other connected device. Additionally, the `ClientConnectionManager` lacks uniqueness checks, allowing an attacker to overwrite existing client registrations by reusing a `client_id`. This combination of flaws allows for unauthorized task execution on peer devices and session hijacking.
Affected products
- Microsoft UFO 3.0.1-4-ge2626659
Timeline
- 2026-05-14: advisory: GitHub Security Advisory published
- 2026-05-27: disclosed: CVE published to NVD