CVE-2026-46402
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMicrosoft 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMicrosoft UFO 3.0.1-4-ge2626659 contains a path traversal vulnerability where the user-controlled task_name parameter is used directly in constructing session log file paths without sanitization, allowing authenticated clients to write log files outside the intended logs/ directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Microsoft UFO installation and versionLocate the UFO installation directory and check for version information in metadata files, about dialog, or by running 'ufo --version' or checking the git commit hash if installed from source. The affected version includes commit ge2626659.Affected if The installed version is 3.0.1-4-ge2626659 or earlier versions prior to the fix for this path traversal issue.
-
Verify authentication is enabled for UFO client connectionsCheck the UFO server configuration for authentication settings. Look for auth_token, password, or session authentication configuration files.Affected if Authentication is disabled or weak, allowing unauthenticated clients to connect and supply the task_name parameter.
-
Identify if task_name parameter handling is exposedLocate the session log creation code or API endpoints that accept task_name. Search for file operations using task_name in path construction for log files.Affected if The application accepts task_name from clients and uses it directly in file path construction without validation.
-
Inspect logs directory isolationCheck the logs/ directory location and verify files written there. Attempt to identify if log files can be created outside the intended logs/ directory through path traversal.Affected if Log files can be written outside the logs/ directory, indicating the vulnerability is exploitable.
A user is affected if they run Microsoft UFO version 3.0.1-4-ge2626659 (or earlier unpatched versions) with authentication enabled for client connections and the task_name parameter is accepted without path traversal validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on the task_name parameter to reject path traversal sequences (../), use allowlist validation for permitted characters, and normalize/canonicalize paths before file operations to ensure files remain within the intended logs directory.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46402 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data