p PatchFirst

CVE-2026-33414

CVE-2026-33414 · PowerShell Command Injection in Podman HyperV Machine

CVSS 4.0 · Medium · EPSS 0.6% · Fix available

Compare with your installed version

Affected products and known fixed versions are public information. Compare them with your installed version.

  • podmanNo fix published
  • podman Debian 13No fix published
  • podman Debian 14Update to 5.8.2+ds1-1
  • podman Ubuntu 25.10No fix published
  • and 2 more

Check the installed version:

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="podman"'

Assess your server’s risks

The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.

Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.

curl -fsSL https://patchfirst.dev/check.sh | sh
Check your server for free →

Channels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Podman is a tool for managing OCI containers and pods. Versions 4.8.0 through 5.8.1 contain a command injection vulnerability in the HyperV machine backend in pkg/machine/hyperv/stubber.go, where the VM image path is inserted into a PowerShell double-quoted string without sanitization, allowing $() subexpression injection. Because PowerShell evaluates subexpressions inside double-quoted strings before executing the outer command, an attacker who can control the VM image path through a crafted machine name or image directory can execute arbitrary PowerShell commands with the privileges of the Podman process. On typical Windows installations this means SYSTEM-level code execution, and only Windows is affected as the code is exclusive to the HyperV backend. This issue has been patched in version 5.8.2.

Published
Updated

Fixes in distributions

Stack: system

Affected products and versions

  • podman

    Versions
    • >= 4.8.0, < 5.8.2: Affected

    No fix published

  • podman Debian 13

    Versions
    • 5.4.2+ds1-2
    • 5.6.1+ds1-1
    • 5.6.1+ds1-2
    • 5.6.1+ds2-2
    • 5.6.1+ds2-3
    • 5.6.2+ds1-1
    All versions (26)
    • 5.6.2+ds1-2
    • 5.6.2+ds1-3
    • 5.6.2+ds1-3+exp1
    • 5.6.2+ds1-4
    • 5.7.0+ds2-1
    • 5.7.0+ds2-2
    • 5.7.0+ds2-3
    • 5.8.0+ds1-1
    • 5.8.1+ds1-1
    • 5.8.1+ds1-2
    • 5.8.1+ds1-3
    • 5.8.2+ds1-1
    • 5.8.2+ds1-2
    • 5.8.2+ds1-3
    • 5.8.3+ds1-1
    • 5.8.4+ds1-1
    • 5.8.4+ds1-2
    • 5.8.6+ds1-1
    • 5.8.6+ds1-2
    • 6.1.1+ds1-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • podman Debian 14

    Versions
    • 5.4.2+ds1-2
    • 5.6.1+ds1-1
    • 5.6.1+ds1-2
    • 5.6.1+ds2-2
    • 5.6.1+ds2-3
    • 5.6.2+ds1-1
    All versions (17)
    • 5.6.2+ds1-2
    • 5.6.2+ds1-3
    • 5.6.2+ds1-3+exp1
    • 5.6.2+ds1-4
    • 5.7.0+ds2-1
    • 5.7.0+ds2-2
    • 5.7.0+ds2-3
    • 5.8.0+ds1-1
    • 5.8.1+ds1-1
    • 5.8.1+ds1-2
    • 5.8.1+ds1-3
    Affected ranges
    • ECOSYSTEM: < 5.8.2+ds1-1

    Update to 5.8.2+ds1-1

  • podman Ubuntu 25.10

    Versions
    • 5.4.1+ds1-1
    • 5.4.2+ds1-1
    • 5.4.2+ds1-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • podman Ubuntu 26.10

    Versions
    • 5.7.0+ds2-3build1
    • 5.8.3+ds1-1
    • 5.8.4+ds1-1
    • 5.8.6+ds1-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • podman Ubuntu 26.04 LTS

    Versions
    • 5.4.2+ds1-2
    • 5.7.0+ds2-3
    • 5.7.0+ds2-3build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →