Github.Com Containers Podman V5 vulnerabilities
7 known vulnerabilities affecting github.com/containers_podman_v5.
Total CVEs
7
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH5MEDIUM2
Vulnerabilities
Page 1 of 1
CVE-2026-33414MEDIUM≥ 0, < 5.8.22026-04-14
CVE-2026-33414 [MEDIUM] CWE-78 PowerShell Command Injection in Podman HyperV Machine
PowerShell Command Injection in Podman HyperV Machine
## Summary
A command injection vulnerability exists in Podman's HyperV machine backend. The VM image path is inserted into a PowerShell double-quoted string without sanitization, allowing `$()` subexpression injection.
## Affected Code
**File**: `pkg/machine/hyperv/stubber.go:647`
```go
resize := exec.Command("powershell", []string{
"-command",
fmt.Sprin
ghsa
CVE-2025-4953HIGH≥ 0, ≤ 5.5.02025-09-16
CVE-2025-4953 [HIGH] CWE-378 Podman Creates Temporary File with Insecure Permissions
Podman Creates Temporary File with Insecure Permissions
A flaw was found in Podman. In a Containerfile or Podman, data written to RUN --mount=type=bind mounts during the podman build is not discarded. This issue can lead to files created within the container appearing in the temporary build context directory on the host, leaving the created files accessible.
ghsaosv
CVE-2025-9566HIGH≥ 0, < 5.6.12025-09-04
CVE-2025-9566 [HIGH] CWE-22 podman kube play symlink traversal vulnerability
podman kube play symlink traversal vulnerability
### Impact
The podman kube play command can overwrite host files when the kube file contains a ConfigMap or Secret volume mount and the volume already contains a symlink to a host file.
This allows a malicious container to write to arbitrary files on the host BUT the attacker only controls the target path not the contents that will be written to the file. The contents a
ghsaosv
CVE-2025-6032HIGH≥ 0, < 5.5.22025-06-25
CVE-2025-6032 [HIGH] CWE-295 Podman Improper Certificate Validation; machine missing TLS verification
Podman Improper Certificate Validation; machine missing TLS verification
### Impact
The podman machine init command fails to verify the TLS certificate when downloading the VM images from an OCI registry (which it does by default since 5.0.0) allowing a possible Man In The Middle attack.
### Patches
https://github.com/containers/podman/commit/726b506acc8a00d99f1a3a1357ecf619a1f798c3
Fixed in v
ghsaosv
CVE-2024-9407MEDIUM≥ 0, < 5.2.42024-10-01
CVE-2024-9407 [MEDIUM] CWE-20 Improper Input Validation in Buildah and Podman
Improper Input Validation in Buildah and Podman
A vulnerability exists in the bind-propagation option of the Dockerfile RUN --mount instruction. The system does not properly validate the input passed to this option, allowing users to pass arbitrary parameters to the mount instruction. This issue can be exploited to mount sensitive directories from the host into a container during the build process and, in some cases,
ghsaosv
CVE-2024-3056HIGH≥ 0, ≤ 5.2.02024-08-02
CVE-2024-3056 [HIGH] CWE-400 Podman vulnerable to memory-based denial of service
Podman vulnerable to memory-based denial of service
A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC resources in /dev/shm. The malicious container will continue to exhaust resources until it is out-of-memory (OOM) killed. While the malicious container's
ghsaosv
CVE-2024-1753HIGHCVSS 8.6≥ 0, < 5.0.12024-03-28
CVE-2024-1753 [HIGH] CWE-269 Podman affected by CVE-2024-1753 container escape at build time
Podman affected by CVE-2024-1753 container escape at build time
### Impact
_What kind of vulnerability is it? Who is impacted?_
Users running containers with root privileges allowing a container to run with read/write access to the host system files when selinux is not enabled. With selinux enabled, some read access is allowed.
### Patches
From @nalind . This is a patch for Buildah (https://github.com
ghsaosv