p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in podman

In den letzten 30 Tagen veröffentlichte Sicherheitslücke für podman: 1. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 10

  1. CVE-2026-121885

    Mittel · CVSS 6.5EPSS 0,39%Keine Korrektur veröffentlicht

    Podman: untrusted image labels allow auto-update to restart arbitrary systemd units

    A flaw was found in Podman. An attacker can trigger a Denial of Service (DoS) by supplying a container image containing crafted metadata labels. Podman's auto-update mechanism improperly trusts these image labels to determine which system services to restart. If a user runs the malicious container and auto-update processes it, arbitrary system services are restarted with the user's privileges, potentially allowing an attacker to shut down the host system when Podman runs with administrative privileges.

    Veröffentlicht Aktualisiert
  2. CVE-2026-94603

    Kritisch · CVSS 10EPSS 0,67%Korrektur verfügbar

    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.

    • Auf 5.8.6+ds1-3 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-19730

    Mittel · CVSS 4.2EPSS 0,13%Korrektur verfügbar

    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

    • Auf 5.8.6+ds1-1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-55686

    Mittel · CVSS 5.3EPSS 0,4%Korrektur verfügbar

    Podman: WORKDIR symlink traversal vulnerability

    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 requires help from an untrusted/malicious process that mutates the host filesystem tree during dereferencing of the WORKDIR path, to trigger a race condition. This vulnerability is fixed in 5.7.1.

    • Auf 5.8.1+ds1-2 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-57231

    Hoch · CVSS 7.5EPSS 0,44%Korrektur verfügbar

    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.

    • Auf 5.8.4+ds1-1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-33414

    Mittel · CVSS 4EPSS 0,63%Korrektur verfügbar

    PowerShell Command Injection in Podman HyperV Machine

    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 sanitization, allowing $() subexpression injection. Because PowerShell evaluates subexpressions inside double-quoted strings before executing the outer command, 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 typical Windows installations th

    • Auf 5.8.2+ds1-1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2025-4953

    Hoch · CVSS 7.4EPSS 0,69%Korrektur verfügbar

    Podman: build context bind mount

    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.

    • Auf 5.3.2+ds1-1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2025-9566

    Hoch · CVSS 8.1EPSS 1,21%Korrektur verfügbar

    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

    • Auf 5.6.1+ds1-2 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →