Podman 6.2 fixes three security issues: CVE-2026-121885, involving systemd handling through image labels; CVE-2026-111361, involving an image-signature check bypass; and CVE-2026-123876, involving a bypass of socket restrictions in a seccomp profile.
The release also adds --validate and --label to podman kube play and --multiple-pods for Kubernetes deployments.
Security fixes
The new version closes three gaps that could threaten the security of systems:
- An issue related to the handling of tags in container images, which could affect the control of system services.
- A weakness in checking digital signatures of images, which could be bypassed.
- A loophole that could allow applications to bypass restrictions placed to control communication with the rest of the operating system.
New features and improvements
In addition to security, version 6.2 brings changes that make daily use easier:
- Better collaboration with Kubernetes: Options for validation and tagging were added, as well as the ability to manage many different groups (pods) at the same time.
- Windows support: Users running Podman via WSL on Windows now enjoy better support for systemd services. To work properly, WSL version 2.5.1 or later is required, with 2.7.5 recommended for smooth networking.
- Automatic updates: The automatic update feature is now also available via remote client.
- Other additions: The ability to select a specific platform when sending images (push) has been added, while the program now reacts correctly to termination signals (Ctrl+C) when executing commands inside containers.
The program managers recommend that users upgrade to version 6.2 to ensure the stability and security of their systems.
>Stay connected with Hacks.gr
Set us as a preferred source on Google and find us on social media.
Preferred source
↗
end of article