RHSA-2026:8325HighCVSS 8.2

Red Hat Security Advisory: buildah, crun, podman, runc, and skopeo security update

Published
April 15, 2026
Last Modified
August 23, 2026

🔗 CVE IDs covered (6)

CVE-2025-31133 →CVE-2025-47913 →CVE-2025-52565 →CVE-2025-52881 →CVE-2025-58183 →CVE-2025-65637 →

📋 Description

CVE-2025-31133 — runc: container escape via 'masked path' abuse due to mount race conditions CVE-2025-47913 — golang.org/x/crypto/ssh/agent: golang.org/x/crypto/ssh/agent: SSH client panic due to unexpected SSH_AGENT_SUCCESS CVE-2025-52565 — runc: container escape with malicious config due to /dev/console mount and related races CVE-2025-52881 — runc: opencontainers/selinux: container escape and denial of service due to arbitrary write gadgets and procfs write redirects CVE-2025-58183 — golang: archive/tar: Unbounded allocation when parsing GNU sparse map CVE-2025-65637 — github.com/sirupsen/logrus: github.com/sirupsen/logrus: Denial-of-Service due to large single-line payload

🎯 Affected products115

  • Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-1:1.26.9-1.el9_0.3.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-1:1.26.9-1.el9_0.3.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-1:1.26.9-1.el9_0.3.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-1:1.26.9-1.el9_0.3.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-1:1.26.9-1.el9_0.3.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-debuginfo-1:1.26.9-1.el9_0.3.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-debuginfo-1:1.26.9-1.el9_0.3.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-debuginfo-1:1.26.9-1.el9_0.3.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-debuginfo-1:1.26.9-1.el9_0.3.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-debugsource-1:1.26.9-1.el9_0.3.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-debugsource-1:1.26.9-1.el9_0.3.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-debugsource-1:1.26.9-1.el9_0.3.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-debugsource-1:1.26.9-1.el9_0.3.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-tests-1:1.26.9-1.el9_0.3.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-tests-1:1.26.9-1.el9_0.3.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-tests-1:1.26.9-1.el9_0.3.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-tests-1:1.26.9-1.el9_0.3.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-tests-debuginfo-1:1.26.9-1.el9_0.3.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-tests-debuginfo-1:1.26.9-1.el9_0.3.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-tests-debuginfo-1:1.26.9-1.el9_0.3.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • buildah-tests-debuginfo-1:1.26.9-1.el9_0.3.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • crun-0:1.14.3-1.el9_0.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • crun-0:1.14.3-1.el9_0.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • crun-0:1.14.3-1.el9_0.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • crun-0:1.14.3-1.el9_0.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • crun-0:1.14.3-1.el9_0.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • crun-debuginfo-0:1.14.3-1.el9_0.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • crun-debuginfo-0:1.14.3-1.el9_0.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • crun-debuginfo-0:1.14.3-1.el9_0.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.0)
  • +85 more not shown

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Potential mitigations for this issue include: * Using user namespaces, with the host root user not mapped into the container's namespace. procfs file permissions are managed using Unix DAC and thus user namespaces stop a container process from being able to write to them. * Not running as a root user in the container (this includes disabling setuid binaries with noNewPrivileges). As above, procfs file permissions are managed using Unix DAC and thus non-root users cannot write to them. * Depending on the maskedPath configuration (the default configuratio nonly masks paths in /proc and /sys), using an AppArmor that blocks unexpectedwrites to any maskedPaths (as is the case with the defaultprofile used by Docker and Podman) will block attempts to exploit this issue. However, CVE-2025-52881 allows an attacker to bypass LSMlabels, and so this mitigation is not helpful when considered incombination with CVE-2025-52881. Workaround: No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability. Workaround: Potential mitigations for this issue include: * Using user namespaces, with the host root user not mapped into the container's namespace. procfs file permissions are managed using Unix DAC and thus user namespaces stop a container process from being able to write to them. * Not running as a root user in the container (this includes disabling setuid binaries with noNewPrivileges). As above, procfs file permissions are managed using Unix DAC and thus non-root users cannot write to them. * The default SELinux policy should mitigate this issue, as the /dev/console bind-mount does not re-label the mount and so the container process should not be able to write to unsafe procfs files. However, CVE-2025-52881 allows an attacker to bypass LSM labels, and so this mitigation is not helpful when considered in combination with CVE-2025-52881. * The default AppArmor profile used by most runtimes will NOT help mitigate this issue, as /dev/console access is permitted. You could create a custom profile that blocks access to /dev/console, but such a profile might break regular containers. In addition, CVE-2025-52881 allows an attacker to bypass LSM labels, and so that mitigation is not helpful when considered in combination with CVE-2025-52881. Workaround: Potential mitigations for this issue include: * Using rootless containers, as doing so will block most of the inadvertent writes (runc would run with reduced privileges, making attempts to write to procfs files ineffective). * Based on our analysis, neither AppArmor or SELinux can protect against the full version of the redirected write attack. The container runtime is generally privileged enough to write to arbitrary procfs files, which is more than sufficient to cause a container breakout. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Mitigation is either unavailable or does not meet Red Hat Product Security standards for usability, deployment, applicability, or stability.

🔗 References (9)