RHSA-2026:4532HighCVSS 8.2

Red Hat Security Advisory: buildah security update

Published
March 12, 2026
Last Modified
September 5, 2026

🔗 CVE IDs covered (4)

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

📋 Description

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-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 products22

  • Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-1:1.29.5-1.el9_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-1:1.29.5-1.el9_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-1:1.29.5-1.el9_2.2.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-1:1.29.5-1.el9_2.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-1:1.29.5-1.el9_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-debuginfo-1:1.29.5-1.el9_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-debuginfo-1:1.29.5-1.el9_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-debuginfo-1:1.29.5-1.el9_2.2.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-debuginfo-1:1.29.5-1.el9_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-debugsource-1:1.29.5-1.el9_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-debugsource-1:1.29.5-1.el9_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-debugsource-1:1.29.5-1.el9_2.2.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-debugsource-1:1.29.5-1.el9_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-tests-1:1.29.5-1.el9_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-tests-1:1.29.5-1.el9_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-tests-1:1.29.5-1.el9_2.2.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-tests-1:1.29.5-1.el9_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-tests-debuginfo-1:1.29.5-1.el9_2.2.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-tests-debuginfo-1:1.29.5-1.el9_2.2.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-tests-debuginfo-1:1.29.5-1.el9_2.2.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • buildah-tests-debuginfo-1:1.29.5-1.el9_2.2.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)

✅ 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: 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 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 (7)