Skip to content

Product

containers github.com/containers/podman/v4 vulnerabilities

24 published CVES affecting containers github.com/containers/podman/v4, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
24
Critical
1
High
10
Medium
12
Low
1
Unscored
0
CISA KEV
0

Latest containers github.com/containers/podman/v4 CVEs

Newest publication first

  1. MediumCVSS 5.3 EPSS 0.40%

    Podman is a tool for managing OCI containers and pods. From 3.0.0 until 5.7.1, running a malicious container image where the WORKDIR path contains a symlink can create a directory or modify ownership on the host filesystem. Modified ownership is less likely to happen as that requ...

  2. MediumCVSS 4.0 EPSS 0.63%

    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 sanitiz...

  3. HighCVSS 7.4 EPSS 0.66%

    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 c...

  4. HighCVSS 8.1 EPSS 1.2%

    There's a vulnerability in podman where an attacker may use the kube play command to overwrite host files when the kube file container a Secrete or a ConfigMap volume mount and such volume contains a symbolic link to a host file path. In a successful attack, the attacker can only...

  5. HighCVSS 8.3 EPSS 0.52%

    A flaw was found in Podman. The podman machine init command fails to verify the TLS certificate when downloading the VM images from an OCI registry. This issue results in a Man In The Middle attack.

  6. MediumCVSS 6.8 EPSS 0.54%

    A Time-of-check Time-of-use (TOCTOU) flaw was found in podman. This issue may allow a malicious user to replace a normal file in a volume with a symlink while exporting the volume, allowing for access to arbitrary files on the host file system.

  7. HighCVSS 8.8 EPSS 4.2%

    A privilege escalation flaw was found in Podman. This flaw allows an attacker to publish a malicious image to a public registry. Once this image is downloaded by a potential victim, the vulnerability is triggered after a user runs the 'podman top' command. This action gives the a...

  8. MediumCVSS 5.9 EPSS 1.1%

    Rootless containers run with Podman, receive all traffic with a source IP address of 127.0.0.1 (including from remote hosts). This impacts containerized applications that trust localhost (127.0.01) connections by default and do not require authentication. This issue affects Podma...

  9. MediumCVSS 5.3 EPSS 1.4%

    An information disclosure vulnerability was found in containers/podman in versions before 2.0.5. When using the deprecated Varlink API or the Docker-compatible REST API, if multiple containers are created in a short duration, the environment variables from the first container wil...

  10. MediumCVSS 5.9 EPSS 1.5%

    A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used...

  11. MediumCVSS 5.5 EPSS 1.4%

    An issue was discovered in Podman in libpod before 1.6.0. It resolves a symlink in the host context during a copy operation from the container to the host, because an undesired glob operation occurs. An attacker could create a container image containing particular symlinks that,...

  12. HighCVSS 8.8 EPSS 0.86%

    It has been discovered that podman before version 0.6.1 does not drop capabilities when executing a container as a non-root user. This results in unnecessary privileges being granted to the container.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.