VulnerableCode Package Details - pkg:deb/debian/podman@5.4.2%2Bds1-2?distro=trixie

Search for packages

Vulnerability	Summary	Fixed by
VCID-24jj-m523-3bdr Aliases: CVE-2026-33414 GHSA-hc8w-h2mf-hp59	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.Sprintf("Resize-VHD \"%s\" %d", imagePath.GetPath(), newSize.ToBytes()), }...) ``` ## Root Cause PowerShell evaluates `$()` subexpressions inside double-quoted strings before executing the outer command. The `fmt.Sprintf` call places the user-controlled image path directly into double quotes without escaping or sanitization. ## Impact 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 the Windows host. On typical Windows installations, this means SYSTEM-level code execution. ## Patch https://github.com/containers/podman/commit/571c842bd357ee626019ea97d030fb772fc654ed The affected code is only used on Windows, all other operating systems are not affected by this and can thus ignore the CVE patch. ## Credit We like to thank Sang-Hoon Choi (@KoreaSecurity) for reporting this issue to us.	5.8.2+ds1-1 Affected by 0 other vulnerabilities.
VCID-6h1q-xus4-4qcs Aliases: CVE-2025-9566 GHSA-wp3j-xq48-xpjw	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 are defined in the yaml file by the end user. ### Requirements to exploit: podman kube play must be used with a ConfigMap or Secret volume mount AND must be run more than once on the same volume. All the attacker has to do is create the malicious symlink on the volume the first time it is started. After that all following starts would follow the symlink and write to the host location. ### Patches Fixed in podman v5.6.1 https://github.com/containers/podman/commit/43fbde4e665fe6cee6921868f04b7ccd3de5ad89 ### Workarounds Don't use podman kube play with ConfigMap or Secret volume mounts. ### PR with test for CI Adding on 9/8/2025 by @TomSweeneyRedHat , this is the PR containing the test in CI: https://github.com/containers/podman/pull/27001	5.6.1+ds1-2 Affected by 0 other vulnerabilities. 5.8.1+ds1-2 Affected by 0 other vulnerabilities. 5.8.1+ds1-3 Affected by 0 other vulnerabilities. 5.8.2+ds1-1 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-24jj-m523-3bdr
Aliases:
CVE-2026-33414
GHSA-hc8w-h2mf-hp59

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.Sprintf("Resize-VHD \"%s\" %d", imagePath.GetPath(), newSize.ToBytes()), }...) ``` ## Root Cause PowerShell evaluates `$()` subexpressions inside double-quoted strings before executing the outer command. The `fmt.Sprintf` call places the user-controlled image path directly into double quotes without escaping or sanitization. ## Impact 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 the Windows host. On typical Windows installations, this means SYSTEM-level code execution. ## Patch https://github.com/containers/podman/commit/571c842bd357ee626019ea97d030fb772fc654ed The affected code is only used on Windows, all other operating systems are not affected by this and can thus ignore the CVE patch. ## Credit We like to thank Sang-Hoon Choi (@KoreaSecurity) for reporting this issue to us.

5.8.2+ds1-1
Affected by 0 other vulnerabilities.

VCID-6h1q-xus4-4qcs
Aliases:
CVE-2025-9566
GHSA-wp3j-xq48-xpjw

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 are defined in the yaml file by the end user. ### Requirements to exploit: podman kube play must be used with a ConfigMap or Secret volume mount AND must be run more than once on the same volume. All the attacker has to do is create the malicious symlink on the volume the first time it is started. After that all following starts would follow the symlink and write to the host location. ### Patches Fixed in podman v5.6.1 https://github.com/containers/podman/commit/43fbde4e665fe6cee6921868f04b7ccd3de5ad89 ### Workarounds Don't use podman kube play with ConfigMap or Secret volume mounts. ### PR with test for CI Adding on 9/8/2025 by @TomSweeneyRedHat , this is the PR containing the test in CI: https://github.com/containers/podman/pull/27001

5.6.1+ds1-2
Affected by 0 other vulnerabilities.

5.8.1+ds1-2
Affected by 0 other vulnerabilities.

5.8.1+ds1-3
Affected by 0 other vulnerabilities.

5.8.2+ds1-1
Affected by 0 other vulnerabilities.

Vulnerability	Summary	Aliases
VCID-fhyv-xgpf-kfdf	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.	CVE-2025-4953 GHSA-m68q-4hqr-mc6f
VCID-tuub-p4f4-nqer	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 v5.5.2 ### Workarounds Download the disk image manually via some other tool that verifies the TLS connection. Then pass the local image as file path (podman machine init --image ./somepath)	CVE-2025-6032 GHSA-65gg-3w2w-hr4h

Vulnerability

Summary

Aliases

VCID-fhyv-xgpf-kfdf

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.

CVE-2025-4953
GHSA-m68q-4hqr-mc6f

VCID-tuub-p4f4-nqer

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 v5.5.2 ### Workarounds Download the disk image manually via some other tool that verifies the TLS connection. Then pass the local image as file path (podman machine init --image ./somepath)

CVE-2025-6032
GHSA-65gg-3w2w-hr4h

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-04-17T22:44:40.052218+00:00	Debian Importer	Affected by	VCID-24jj-m523-3bdr	https://security-tracker.debian.org/tracker/data/json	38.4.0
2026-04-17T22:44:40.023410+00:00	Debian Importer	Affected by	VCID-6h1q-xus4-4qcs	https://security-tracker.debian.org/tracker/data/json	38.4.0
2026-04-16T10:05:20.975207+00:00	Debian Importer	Fixing	VCID-fhyv-xgpf-kfdf	https://security-tracker.debian.org/tracker/data/json	38.4.0
2026-04-16T09:47:57.737512+00:00	Debian Importer	Fixing	VCID-tuub-p4f4-nqer	https://security-tracker.debian.org/tracker/data/json	38.4.0
2026-04-12T18:15:28.359787+00:00	Debian Importer	Affected by	VCID-6h1q-xus4-4qcs	https://security-tracker.debian.org/tracker/data/json	38.3.0
2026-04-12T18:15:28.330659+00:00	Debian Importer	Fixing	VCID-tuub-p4f4-nqer	https://security-tracker.debian.org/tracker/data/json	38.3.0
2026-04-12T18:15:28.302363+00:00	Debian Importer	Fixing	VCID-fhyv-xgpf-kfdf	https://security-tracker.debian.org/tracker/data/json	38.3.0
2026-04-03T07:50:06.039718+00:00	Debian Importer	Affected by	VCID-6h1q-xus4-4qcs	https://security-tracker.debian.org/tracker/data/json	38.1.0
2026-04-03T07:50:06.022987+00:00	Debian Importer	Fixing	VCID-tuub-p4f4-nqer	https://security-tracker.debian.org/tracker/data/json	38.1.0
2026-04-03T07:50:05.998331+00:00	Debian Importer	Fixing	VCID-fhyv-xgpf-kfdf	https://security-tracker.debian.org/tracker/data/json	38.1.0