Quick answers
- Is CVE-2026-46402 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46402 being exploited in the wild.
- How severe is CVE-2026-46402?
- High severity, with a CVSS score of 8.1, published 27 May 2026.
- Which products and versions are affected?
- Microsoft UFO 3.0.1-4-ge2626659.
- Is there a fix for CVE-2026-46402?
- 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-46402 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-46402?
- 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
A path traversal vulnerability exists in Microsoft UFO version 3.0.1-4-ge2626659 due to improper sanitization of the 'task_name' parameter. The UFO server accepts this value via WebSocket or HTTP task requests and passes it directly to the BaseSession class, which constructs a filesystem path using an f-string (f"logs/{task}/"). Because the application calls os.makedirs() and subsequent file write operations on this unsanitized path, an authenticated attacker can use traversal sequences (e.g., '../') to create directories and log files (response.log, request.log, evaluation.log) anywhere the server process has write permissions. This can lead to arbitrary file creation or integrity issues on the host system. As of the advisory date, no patched version is specified.
Affected products
- Microsoft UFO 3.0.1-4-ge2626659
Timeline
- 2026-05-13: advisory: GitHub advisory published by maintainers
- 2026-05-27: disclosed: CVE published to NVD