Quick answers
- Is CVE-2026-46416 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46416 being exploited in the wild.
- How severe is CVE-2026-46416?
- Medium severity, with a CVSS score of 6.3, published 27 May 2026.
- Which products and versions are affected?
- Microsoft UFO 3.0.1-4-ge2626659.
- Is there a fix for CVE-2026-46416?
- 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-46416 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-46416?
- 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 UFOWebSocketHandler within 'ufo/server/app.py' and 'ufo/server/ws/handler.py'. The framework initializes a single shared handler instance for all '/ws' connections and stores per-connection protocol objects (such as transport, heartbeat, and task protocols) in mutable instance fields. When a new client connects, it overwrites these shared fields with its own connection state. Subsequent message handlers then use these shared fields to route responses, causing the server to send data (such as device_info_response or task acknowledgments) to the most recently connected client rather than the client that originated the request. This results in an authenticated cross-client WebSocket response hijack.
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