Microsoft UFO uses untrusted task_name in log paths, allowing authenticated path traversal and log file creation outside the logs directory

published 2026-05-27 5 mo ago modified 2026-10-26 13 d ago also EUVD-2026-32674

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

Microsoft UFO open-source framework for intelligent automation across devices and platforms. In 3.0.1-4-ge2626659, Microsoft UFO uses the user-controlled task_name value directly when constructing session log paths. An authenticated client can supply path traversal sequences in task_name and cause UFO to create log directories and log files outside the intended logs/ directory.

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 5 mo ago (2026-05-30)

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/microsoft/UFO/security/advisories/GHSA-whcg-fgpx-76f2 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Affected products

microsoft UFO

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory
CWE-73 External Control of File Name or Path

References

github.com /microsoft/UFO/security/advisories/GHSA-whcg-fgpx-76f2
exploit

Sources

CVE List CVE-2026-46402
NVD CVE-2026-46402

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary