dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-45322

HIGH · 7.8 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Microsoft UFO open-source framework for intelligent automation across devices and platforms. Microsoft UFO tagged releases up to and including v3.0.0 contain an OS command injection vulnerability in the shell action replay path. In affected releases, ShellReceiver.run_shell() passes a command string from action parameters directly to subprocess.Popen() with shell=True and executable=powershell.exe. The same shell-execution behavior is also reachable through ShellReceiver.execute_command(). The shell receiver is invoked by action classes such as RunShellCommand.execute() and ExecuteCommand.execute(), which forward stored action parameters to the shell receiver. Because UFO stores planned and executed actions in per-session JSON records, an attacker who can write or modify a session/action JSON file can plant a shell action. When the session is resumed or replayed, UFO executes the attacker's command as the UFO process user.

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 · high confidence

OS command injection vulnerability in Microsoft UFO framework (versions up to v3.0.0) where ShellReceiver.run_shell() passes unsanitized action parameters directly to subprocess.Popen() with shell=True and executable=powershell.exe. Attackers with write access to session/action JSON files can plant malicious shell commands that execute when the session is resumed or replayed.

MitigationReplace shell=True with shell=False in subprocess.Popen() calls and validate/sanitize all command parameters before execution. Additionally, implement integrity verification for session JSON files to prevent tampering.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Microsoft UFO framework installation and version
    Locate the UFO framework package in your environment and retrieve its version (e.g., via pip show, package manager, or inspecting version metadata files). Compare the installed version against the affected range: versions up to and including v3.0.0.
    Affected if Installed version is v3.0.0 or earlier
  2. Locate the ShellReceiver.run_shell() method
    Search the codebase for the ShellReceiver class and its run_shell() method. This is typically in a file related to shell execution or receiver functionality within the UFO framework.
    Affected if The method exists in your installation
  3. Inspect subprocess.Popen() call in run_shell()
    Open the file containing run_shell() and examine the subprocess.Popen() call. Look for the presence of shell=True and executable=powershell.exe parameters.
    Affected if shell=True and executable=powershell.exe are both present in the Popen call
  4. Check for unsanitized action parameter usage
    Review the code between parameter input and the subprocess.Popen() call. Determine whether action parameters (from JSON files) are passed directly to Popen() without validation, sanitization, or filtering.
    Affected if Action parameters are passed to Popen() without sanitization or validation
  5. Assess session/action JSON file integrity controls
    Examine how the framework loads session and action JSON files. Determine if there are integrity verification mechanisms (signatures, checksums, access controls) in place to prevent tampering of these files.
    Affected if No integrity verification exists for session/action JSON files, or write access is uncontrolled

Your environment is affected if you have Microsoft UFO framework v3.0.0 or earlier with ShellReceiver.run_shell() using subprocess.Popen(shell=True, executable=powershell.exe) on unsanitized action parameters from JSON files that lack integrity controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace shell=True with shell=False in subprocess.Popen() calls and validate/sanitize all command parameters before execution. Additionally, implement integrity verification for session JSON files to prevent tampering.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45322 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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