Quick answers
- Is CVE-2026-105792 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105792 being exploited in the wild.
- How severe is CVE-2026-105792?
- Medium severity, with a CVSS score of 6.5, published 6 October 2026.
- Which products and versions are affected?
- Microsoft UFO before 3.0.9.
- Is there a fix for CVE-2026-105792?
- Yes: fixed in 3.0.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105792 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105792?
- 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.
How to fix
- Fixed in: 3.0.9
Technical details
The /api/task_result/{task_name} endpoint in ufo/server/services/session_manager.py attempts to acquire a non-reentrant lock twice when processing a task name that maps to an existing session—first in get_result_by_task() and again in the nested get_result() call—causing a deadlock. An authenticated attacker who knows or creates a mapped task name can trigger this condition. In the default single-process server configuration, the blocked event-loop thread prevents other requests and background tasks from executing.
Affected products
- Microsoft UFO before 3.0.9
Timeline
- 2026-10-06: disclosed
- 2026-09-14: patched