CVE-2024-3056
HighCVSS 7.7Exploitation Probability (EPSS)
Low risk45th percentile - higher than 45% of all known CVEs
Summary
A flaw in Podman allows an attacker to create a specially crafted container that, when sharing IPC with another container, creates a large number of IPC resources in /dev/shm. The malicious container exhausts resources until OOM-killed, but the IPC resources remain in the IPC namespace, and with automatic restarts this leads to memory exhaustion of the system.
Risk Assessment
This can result in a memory-based denial of service, making the host system and its services unavailable.
Recommendation
Update Podman to a patched version and avoid --restart=always for containers sharing IPC with untrusted containers.
Other vulnerabilities in Podman
See all- CVE-2026-94603Critical
Podman from 4.4.0 until 5.8.8 and 6.1.3 treats an image carrying the io.podman.annotations.checkpoint.runtime.name annotation as a checkpoint and silently ignores user-supplied container creation restrictions such as --cap-drop=ALL. This allows image-controlled checkpoint state to select weaker sandbox settings and capabilities. Rootless containers are not affected because checkpoint and restore are unavailable in that mode. This issue is fixed in versions 5.8.8 and 6.1.3.
- CVE-2025-11395Medium
A flaw was found in Podman. If an attacker can pass a crafted tar archive to the `podman load` command, they can create files on the host machine with the privileges of the user running Podman.
- CVE-2026-19730Medium
The 'podman quadlet install --replace' command opens the existing Quadlet file without O_TRUNC, which on filesystems without reflink support (e.g., default XFS on RHEL) leads to incomplete overwriting. If the new Quadlet is shorter than the original, old data remains at the end of the file, and the command completes without warning.
- CVE-2026-57231High
Podman from version 1.8.1 to 5.8.4 contains a vulnerability where a container image with an environment variable consisting only of a key (no value) can trick Podman into passing that variable from the host into the container. Using an asterisk (*) as the key causes all host environment variables to be passed, allowing a malicious image to exfiltrate Podman environment variables from the session where the container is launched.
- CVE-2026-33414High
Podman versions 4.8.0 through 5.8.1 contain a command injection vulnerability in the HyperV backend, where the VM image path is inserted into a PowerShell string without sanitization, allowing arbitrary PowerShell commands to be executed with Podman process privileges (SYSTEM on Windows).
- CVE-2025-4953High
A flaw in Podman causes data written to `RUN --mount=type=bind` mounts during `podman build` to persist, making files created inside the container appear in the host's temporary build context directory.
- CVE-2025-9566High
A vulnerability in Podman allows an attacker to overwrite host files using the 'kube play' command when the kube file contains a Secret or ConfigMap volume mount with a symbolic link to a host file path. The attacker can control which file is overwritten but not the content written.
- CVE-2025-6032High
A flaw was found in Podman where the `podman machine init` command fails to verify the TLS certificate when downloading VM images from an OCI registry. This enables a Man-in-the-Middle (MITM) attack.
- CVE-2024-11218High
A vulnerability in `podman build` and `buildah` allows container breakout via a race condition with --jobs=2 when building a malicious Containerfile. Even with SELinux enabled, it allows enumeration of files and directories on the host.
Original NVD description (English source)
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 cgroup will be removed, the IPC resources it created are not. Those resources are tied to the IPC namespace that will not be removed until all containers using it are stopped, and one non-malicious container is holding the namespace open. The malicious container is restarted, either automatically or by attacker control, repeating the process and increasing the amount of memory consumed. With a container configured to restart always, such as `podman run --restart=always`, this can result in a memory-based denial of service of the system.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS