CVE-2026-33414: Podman is a tool for managing OCI containers and pods

This month

HIGH 7.8UPGRADE

CVE-2026-33414 is a high-severity flaw (CVSS 7.8) affecting podman. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-78, CWE-94
Published	2026-04-14
Last modified	2026-07-24

Publisher (CNA): GitHub, Inc. · Vendor: podman project

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-14 23:16 UTCPublished CVE record published
2026-07-24 23:10 UTCUpdated Record last modified

podman project podman UPGRADE

Affected: >= 4.8.0 and < 5.8.2

Fixed in: 5.8.2

Safe to downgrade to: a release before 4.8.0

1. Check installed version

apt-cache policy podman || rpm -q podman || podman --version

2. UPGRADE to 5.8.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade podman

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade podman

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.8.0 (Debian / Ubuntu)

apt-cache madison podman sudo apt install podman=<VERSION_BEFORE_4.8.0> sudo apt-mark hold podman

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list podman sudo dnf downgrade podman-<VERSION_BEFORE_4.8.0> sudo dnf versionlock add podman

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33414?

podman: upgrade to 5.8.2. Exact commands for each OS are on this page.

Is CVE-2026-33414 being exploited?

CVE-2026-33414 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33414 affect?

CVE-2026-33414 affects podman. Severity is high (CVSS 7.8). 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 PowerSh

How urgent is CVE-2026-33414?

Priority 40/100. High severity

Software pages

PowerShell vulnerabilities · Podman vulnerabilities

Related CVEs

CVE-2026-57231 HIGH 7.5 UPGRADE Podman is a tool for managing OCI containers and pods
CVE-2026-55686 MEDIUM 5.3 UPGRADE Podman is a tool for managing OCI containers and pods

References

← Back to latest CVEs