Critical Security Update for Podman: Addressing Multiple Vulnerabilities
Summary
ALSA-2026:3336: Important: podman security update. Affects podman versions < 7:5.6.0-12.el10_1.alma.1. Fixed in 7:5.6.0-12.el10_1.alma.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Podman is a container management tool that allows users to manage pods, container images, and containers without requiring a daemon. It is part of the libpod library, which is essential for applications that utilize container pods, a concept integral to Kubernetes. Podman provides a user-friendly interface for managing containerized applications, making it a popular choice among developers and system administrators. However, recent vulnerabilities have been identified that could potentially compromise the security and performance of applications utilizing Podman.
Vulnerability Detail
The vulnerabilities identified in Podman include Denial of Service (DoS) due to excessive resource consumption from crafted certificates (CVE-2025-61729), excessive CPU usage when building archive indexes (CVE-2025-61728), memory exhaustion during query parameter parsing (CVE-2025-61726), and unexpected session resumption in TLS (CVE-2025-68121). These vulnerabilities can lead to significant performance degradation and potential service outages, affecting the reliability of applications that depend on Podman for container management.
How To Fix
Minimum fixed version
7:5.6.0-12.el10_1.alma.1
This is the first release that contains the fix.
sudo dnf update podmanTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, you can limit the resource usage of Podman by configuring resource limits in your container specifications. This may help mitigate the impact of the vulnerabilities until a full update can be applied.
Conclusion
In summary, the recent vulnerabilities identified in Podman pose significant risks to applications relying on this container management tool. It is crucial to update to the patched version to mitigate these risks and ensure the security and performance of your containerized applications.
See every vulnerability recorded for podman →
FAQ
Podman is a container management tool that allows users to create and manage containers and pods without requiring a daemon.
The main vulnerabilities include Denial of Service due to excessive resource consumption, excessive CPU usage, memory exhaustion, and unexpected session resumption in TLS.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.
If you cannot update Podman immediately, consider implementing resource limits in your container specifications as a temporary workaround.
For more details, refer to the CVE pages listed in the related section of the vulnerability report.
Related vulnerabilities
Recent vulnerabilities recorded for podman.
