p PatchFirst

PatchFirst · Latest vulnerabilities

podman vulnerabilities

Vulnerabilities published for podman in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 23

  1. CVE-2025-52881

    High · CVSS 7.3EPSS 0.78%Fix available

    runc: LSM labels can be bypassed with malicious config using dummy procfs files

    runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7, 1.3.2 and 1.4.0-rc.2, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (we have also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts. While similar, the mitigation applied for the

    • Update to 5.7.0-r0
    Published Updated
  2. CVE-2025-9566

    High · CVSS 8.1EPSS 1.21%Fix available

    Podman: podman kube play command may overwrite host files

    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 control the target file to be overwritten but not the content to be written into the file. Binary-Affected: podman Upstream-version-introduced: v4.0.0 Upstream-version-fixed: v5.6.1

    • Update to 5.6.1-r0
    Published Updated
  3. CVE-2024-11218

    High · CVSS 8.6EPSS 0.36%Fix available

    Podman: buildah: container breakout by using --jobs=2 and a race condition when building a malicious containerfile

    A vulnerability was found in `podman build` and `buildah.` This issue occurs in a container breakout by using --jobs=2 and a race condition when building a malicious Containerfile. SELinux might mitigate it, but even with SELinux on, it still allows the enumeration of files and directories on the host.

    • Update to 5.3.2-r0
    Published Updated
  4. CVE-2024-9676

    Medium · CVSS 6.5EPSS 1.32%Fix available

    Podman: buildah: cri-o: symlink traversal vulnerability in the containers/storage library can cause denial of service (dos)

    A vulnerability was found in Podman, Buildah, and CRI-O. A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and CRI-O to hang and result in a denial of service via OOM kill when running a malicious image using an automatically assigned user namespace (`--userns=auto` in Podman and Buildah). The containers/storage library will read /etc/passwd inside the container, but does not properly validate if that file is a symlink, which can be used to cause the library to read an arbitrary file on the host.

    • Update to 5.2.5-r0
    Published Updated
  5. CVE-2024-9675

    High · CVSS 7.8EPSS 0.39%Fix available

    Buildah: buildah allows arbitrary directory mount

    A vulnerability was found in Buildah. Cache mounts do not properly validate that user-specified paths for the cache are within our cache directory, allowing a `RUN` instruction in a Container file to mount an arbitrary directory from the host (read/write) into the container as long as those files can be accessed by the user running Buildah.

    • Update to 5.2.5-r0
    Published Updated
  6. CVE-2024-9407

    Medium · CVSS 4.7EPSS 0.29%Fix available

    Buildah: podman: improper input validation in bind-propagation option of dockerfile run --mount instruction

    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, modify the contents of those mounted files. Even if SELinux is used, this vulnerability can bypass its protection by allowing the source directory to be relabeled to give the container access to host files.

    • Update to 5.2.4-r0
    Published Updated
  7. CVE-2024-9341

    Medium · CVSS 5.4EPSS 1.03%Fix available

    Podman: buildah: cri-o: fips crypto-policy directory mounting issue in containers/common go library

    A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the system into mounting sensitive host directories inside a container. This issue also allows attackers to access critical host files, bypassing the intended isolation between containers and the host system.

    • Update to 5.2.4-r0
    Published Updated
  8. CVE-2024-3727

    High · CVSS 8.3EPSS 1.28%Fix available

    Containers/image: digest type does not guarantee valid type

    A flaw was found in the github.com/containers/image library. This flaw allows attackers to trigger unexpected authenticated registry accesses on behalf of a victim user, causing resource exhaustion, local path traversal, and other attacks.

    • Update to 5.0.3-r0
    Published Updated
  9. CVE-2024-1753

    High · CVSS 8.6EPSS 0.46%Fix available

    Buildah: buildah: container escape via improper bind mount validation

    A flaw was found in Buildah (and subsequently Podman Build) which allows containers to mount arbitrary locations on the host filesystem into build containers. A malicious Containerfile can use a dummy image with a symbolic link to the root filesystem as a mount source and cause the mount operation to mount the host root filesystem inside the RUN step. The commands inside the RUN step will then have read-write access to the host filesystem, allowing for full container escape at build time.

    • Update to 4.9.4-r0
    Published Updated
  10. CVE-2024-23653

    Critical · CVSS 9.8EPSS 4.13%Fix available

    BuildKit interactive containers API does not validate entitlements check

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.

    • Update to 4.9.2-r0
    Published Updated
  11. CVE-2024-23652

    Critical · CVSS 10EPSS 2.46%Fix available

    BuildKit possible host system access from mount stub cleaner

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.

    • Update to 4.9.2-r0
    Published Updated
  12. CVE-2024-23651

    High · CVSS 8.7EPSS 0.91%Fix available

    BuildKit possible race condition with accessing subpaths from cache mounts

    BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with --mount=type=cache,source=... options.

    • Update to 4.9.2-r0
    Published Updated
  13. CVE-2023-48795

    Medium · CVSS 5.9EPSS 93.55%Public exploitFix available

    CVE-2023-48795

    The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with E

    • Update to 4.8.2-r1
    Published Updated
  14. CVE-2023-0778

    Medium · CVSS 6.8EPSS 0.54%Fix available

    CVE-2023-0778

    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.

    • Update to 4.4.2-r0
    Published Updated
  15. CVE-2022-2989

    High · CVSS 7.1EPSS 0.33%Fix available

    CVE-2022-2989

    An incorrect handling of the supplementary groups in the Podman container engine might lead to the sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.

    • Update to 4.3.0-r0
    Published Updated
  16. CVE-2022-27649

    High · CVSS 7.5EPSS 1.43%Fix available

    CVE-2022-27649

    A flaw was found in Podman, where containers were started incorrectly with non-empty default permissions. A vulnerability was found in Moby (Docker Engine), where containers were started incorrectly with non-empty inheritable Linux process capabilities. This flaw allows an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs.

    • Update to 4.0.3-r0
    Published Updated
  17. CVE-2021-3602

    Medium · CVSS 5.5EPSS 0.32%Fix available

    CVE-2021-3602

    An information disclosure flaw was found in Buildah, when building containers using chroot isolation. Running processes in container builds (e.g. Dockerfile RUN commands) can access environment variables from parent and grandparent processes. When run in a container in a CI/CD environment, environment variables may include sensitive information that was shared with the container in order to be used only by Buildah itself (e.g. container registry credentials).

    • Update to 3.2.3-r0
    Published Updated
  18. CVE-2021-4024

    Medium · CVSS 6.5EPSS 1.14%Fix available

    CVE-2021-4024

    A flaw was found in podman. The `podman machine` function (used to create and manage Podman virtual machine containing a Podman process) spawns a `gvproxy` process on the host system. The `gvproxy` API is accessible on port 7777 on all IP addresses on the host. If that port is open on the host's firewall, an attacker can potentially use the `gvproxy` API to forward ports on the host to ports in the VM, making private services on the VM accessible to the network. This issue could be also used to interrupt the host's services by forwarding all ports to the VM.

    • Update to 3.4.4-r0
    Published Updated
  19. CVE-2021-41190

    Low · CVSS 3EPSS 2.22%Fix available

    Clarify Content-Type handling in OCI spec

    The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently. The OCI Distribution Specification has been updated to require tha

    • Update to 3.4.4-r0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →