CVE-2026-33414: PowerShell Command Injection in Podman HyperV Machine
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-33414 is a high-severity Podman flaw affecting Windows HyperV machine use. A local attacker who can influence a VM image path or related machine input could make Podman run unintended PowerShell commands with Podman’s privileges, commonly SYSTEM on Windows. Podman 5.8.2 contains the fix.
Executive priority
Treat this as a priority patch for Windows engineering and build environments. The affected population may be narrow, but successful exploitation could give high-impact code execution under powerful local privileges.
Technical view
Podman 4.8.0 through 5.8.1 insert the HyperV VM image path into a PowerShell double-quoted string without sanitization in pkg/machine/hyperv/stubber.go. PowerShell expands subexpressions inside double quotes, enabling command injection when an attacker controls the image path through a crafted machine name or image directory.
Likely exposure
Exposure is limited to Windows systems using Podman’s HyperV machine backend with versions 4.8.0 through 5.8.1. Linux, macOS, and non-HyperV backends are not identified as affected in the provided sources.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The attack is local, low-complexity, requires low privileges, and does not require user interaction once the attacker can control the relevant Podman machine path input.
Researcher notes
The evidence points to unsafe PowerShell string construction and a patch commit correcting the affected HyperV backend path handling. Do not assume broader platform impact, remote exploitability, or active exploitation from the supplied sources.
Mitigation direction
Upgrade affected Windows Podman installations to version 5.8.2 or later.
Prioritize developer workstations, build hosts, and CI runners using Podman with HyperV.
Restrict untrusted local users from creating or modifying Podman machine paths until patched.
Review vendor advisories for platform-specific package availability and operational guidance.
Validation and detection
Inventory Windows hosts running Podman versions 4.8.0 through 5.8.1.
Confirm whether the HyperV machine backend is enabled or used.
Verify upgraded hosts report Podman version 5.8.2 or later.
Review endpoint telemetry for unusual PowerShell child activity associated with Podman processes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.