RHSA-2026:97533: Important: podman security, bug fix, and enhancement update
The podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes.Security Fix(es): golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted AES-GCM packet decoder inputs (CVE-2026-46597) Bug Fix(es) and Enhancement(s): When using --mount in podman run results can be inconsistent, especially on /var/tmp (JIRA:RHEL-154348) [RFE] SELinux confined users unable to start podman.socket systemd user service (JIRA:RHEL-132875) [RFE] Mounting of NFS Quadlet volume fails with permission denied (JIRA:RHEL-145863) [RFE] podman API socket to support TLS/mTLS (JIRA:RHEL-91221) Rebase podman to the latest upstream release [rhel-9.9] (JIRA:RHEL-168737) podman does not clean up all files and leaves orphaned files consuming disk space [rhel-9.9] (JIRA:RHEL-173976) [FJ9.8 Bug]: [REG]The "podman-remote save" command fails for rootless users. (JIRA:RHEL-186006) podman: rebase to 5.8.5 (JIRA:RHEL-212537) [FJ9.9 Bug]: [REG]The "podman rm" command can accidentally delete containers even though it is mounted by Buildah when used by a rootless user in remote. (JIRA:RHEL-211092) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.Additional Changes:For detailed information on changes in this release, see the Red Hat Enterprise Linux 9 Release Notes linked from the References section.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/podmanto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-debuginfoto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-debugsourceto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-dockerto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-pluginsto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-plugins-debuginfoto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-remoteto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-remote-debuginfoto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-teststo a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podman-tests-debuginfoto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9 - Upgrade
Upgrade
redhat/podmanto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
redhat/podman-debuginfoto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
redhat/podman-debugsourceto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
redhat/podman-pluginsto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
redhat/podman-plugins-debuginfoto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
redhat/podman-remoteto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
redhat/podman-remote-debuginfoto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
redhat/podman-teststo a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
redhat/podman-tests-debuginfoto a version that resolves this vulnerability.Fixed in 5.8.5-2.el9.aa - Upgrade
Upgrade
podmanto a version that resolves this vulnerability.Fixed in 5.8.5
Event History
Frequently Asked Questions
Which package variants should be included when planning this update?
The advisory lists podman, podman-remote, podman-plugins, podman-tests, and their corresponding debuginfo or debugsource packages.
Does the advisory specify an affected version range or a target fixed version?
No. The provided advisory data does not include affected package versions or a fixed package version.
Are exploitation prerequisites, affected default configurations, or temporary mitigations provided?
No. The provided data identifies a denial-of-service issue involving crafted AES-GCM packet decoder inputs, but does not state exploitation prerequisites, default-configuration exposure, or compensating controls.