NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 16/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: containers podman 5.8.2.

Low priority for now. Upgrade to containers podman 5.8.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.0 · v4.0—No exploit Fix available

Published: Apr 14, 2026
Updated: Jul 24, 2026
EPSS: 0.6% · 49th percentile
CWE: CWE-78

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 16 / 40 · 4.0 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 4.0; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
podman project	podman	cpe:2.3:a:podman_project:podman
microsoft	windows	cpe:2.3:o:microsoft:windows

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

podman project podman4.8.0 and later · before 5.8.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

containers podman
- >= 4.8.0, < 5.8.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:13	podman	from 0	—
Debian:14	podman	before 5.8.2+ds1-1	5.8.2+ds1-1
Go	github.com/containers/podman	from 0	—
Go	github.com/containers/podman/v2	from 0	—
Go	github.com/containers/podman/v3	from 0	—
Go	github.com/containers/podman/v4	from 4.8.0 · up to and including 4.9.5	—
Go	github.com/containers/podman/v4	from 4.8.0	—
Go	github.com/containers/podman/v5	before 5.8.2	5.8.2
openSUSE:Tumbleweed	podman	before 5.8.2-1.1	5.8.2-1.1
Red Hat:hummingbird:1	podman	before 0:5.8.2-1.hum1	0:5.8.2-1.hum1
Red Hat:hummingbird:1	podman-docker	before 0:5.8.2-1.hum1	0:5.8.2-1.hum1
Red Hat:hummingbird:1	podman-machine	before 0:5.8.2-1.hum1	0:5.8.2-1.hum1
Red Hat:hummingbird:1	podman-remote	before 0:5.8.2-1.hum1	0:5.8.2-1.hum1
Red Hat:hummingbird:1	podman-tests	before 0:5.8.2-1.hum1	0:5.8.2-1.hum1
Red Hat:hummingbird:1	podmansh	before 0:5.8.2-1.hum1	0:5.8.2-1.hum1

Same product

podman project: all records

Other highest-scoring records for the same primary product.

CVE-2022-1227A privilege escalation flaw was found in Podman.
36Monitor
CVE-2026-57231Podman: Malformed Image can trick podman run into leaking host environment variables into the container
30Monitor
CVE-2024-3056Podman: kernel: containers in shared ipc namespace are vulnerable to denial of service attack
30Monitor

Published before and after this one in the same product

← EarlierCVE-2022-4123Dec 8, 2022 · A flaw was found in Buildah.
13Monitor
← EarlierCVE-2023-0778Mar 27, 2023 · A Time-of-check Time-of-use (TOCTOU) flaw was found in podman.
27Monitor
Later →CVE-2026-55686Jun 26, 2026 · Podman: WORKDIR symlink traversal vulnerability
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
containers podman	5.8.2 · description	Vendor (CNA)
debian:podman	5.8.2+ds1-1 · Debian:14	Package registry (OSV)
Go:github.com/containers/podman/v5	5.8.2	Package registry (OSV)
opensuse:podman	5.8.2-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:podman	0:5.8.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:podman-docker	0:5.8.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:podman-machine	0:5.8.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:podman-remote	0:5.8.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:podman-tests	0:5.8.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:podmansh	0:5.8.2-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

containers/podmancommit 571c842

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
Administrator privileges are required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Local
Attack complexity: High
Privileges required: High
User interaction: None
Scope: X

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/containers/podman/commit/571c842bd357ee626019ea97d030fb772fc654ed

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records