p PatchFirst

PatchFirst · Latest vulnerabilities

podman vulnerabilities

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

Filter vulnerabilities
Clear filters

Vulnerabilities: 32

  1. CVE-2026-123876

    Medium · CVSS 4.4EPSS 0.22%Fix available

    Podman: containers-common: containers-common: default seccomp af_vsock/netlink_audit deny rules bypassable via 32-bit truncation

    A flaw was found in the default seccomp profile used by Podman via containers-common. Deny rules for AF_VSOCK and NETLINK_AUDIT compared socket arguments with unmasked 64-bit equality. Because the kernel truncates those int arguments to 32 bits, setting upper bits can bypass the deny rules.

    • Update to 5.8.10-r0
    Published Updated
  2. CVE-2026-94603

    Critical · CVSS 10EPSS 0.67%Fix available

    Podman: The `podman run` command can be instructed to disable almost all sandboxing by image annotation

    Podman is a tool for managing OCI containers and pods. From 4.4.0 until 5.8.8 and 6.1.3, podman run 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, allowing 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.

    • Update to 5.8.8-r0
    Published Updated
  3. CVE-2026-107935

    Critical · CVSS 9.3EPSS 0.24%Fix available

    Gvisor-tap-vsock: gvisor-tap-vsock: unathenticated arbitrary file deletion on the host via /expose

    A path traversal vulnerability was found in gvproxy, the network forwarder provided by the gvisor-tap-vsock package. The unauthenticated /services/forwarder/expose endpoint does not validate the caller-supplied socket path, allowing an attacker to delete arbitrary files on the host system.

    • Update to 5.8.9-r0
    Published Updated
  4. CVE-2026-79699

    Medium · CVSS 4.4EPSS 0.23%Fix available

    Podman: buildah: skopeo: containers/storage: malicious tar whiteout header allows replacement of extraction destination directory

    A flaw was found in the containers/storage library. A crafted tar archive containing a malicious whiteout header (e.g. victim/.wh.) can cause the extraction destination directory to be replaced with an arbitrary file when processed by storage/pkg/archive.UnpackLayer, ApplyLayer, or ApplyUncompressedLayer.

    • Update to 5.8.8-r0
    Published Updated
  5. CVE-2026-79705

    Medium · CVSS 4.5EPSS 0.41%Fix available

    Podman: buildah: buildah/copier: directory escape via crafted tar symlinks when used outside buildah by non-root callers

    A flaw was found in the buildah/copier Go package. When used outside of Buildah by a non-root caller, a crafted tar archive containing malicious symlinks can escape the target extraction directory and create files outside the intended destination. Buildah itself uses chroot hardening and is not affected.

    • Update to 5.8.8-r0
    Published Updated
  6. CVE-2026-44517

    Medium · CVSS 6.3EPSS 0.18%Fix available

    Buildah: Build breakout using malicious Containerfile and Git Smart HTTP server or GitHub release tar archive

    Buildah is a tool that facilitates building OCI images. From 1.38.1 until 1.43.2 and 1.44.0, TempDirForURL in define/types.go does not securely confine Git repository subdirectories to the downloaded build context, and downloadToDirectory and stdinToDirectory can follow a Dockerfile symlink left by a partially extracted tar archive. A malicious server supplying a Git repository or tar archive can cause files outside the build context directory to be included in the context or copied into the build. This issue is fixed in versions 1.43.2 and 1.44.0.

    • Update to 5.8.3-r0
    Published Updated
  7. CVE-2026-19730

    Medium · CVSS 4.2EPSS 0.13%Fix available

    Podman: podman: quadlet install --replace non-truncating write retains removed host-access directives

    The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning. There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would o

    • Update to 5.8.6-r0
    Published Updated
  8. CVE-2026-57231

    High · CVSS 7.5EPSS 0.44%Fix available

    Podman: Malformed Image can trick podman run into leaking host environment variables into the container

    Podman is a tool for managing OCI containers and pods. From 1.8.1 until 5.8.4, a container image that contains a environment variable with just a key and no value can trick podman into passing that variable from the host into the container. This is made worse by the fact that using an asterisk (*) will cause podman to pass all host variables into the container. So essentially a malicious image can exfiltrate all podman environment variables that are set in the session from where the container is launched. This vulnerability is fixed in 5.8.4 and 6.0.0.

    • Update to 5.8.6-r0
    Published Updated
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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

Check your server

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

Check your server →