Releases: podman-container-tools/podman
Releases · podman-container-tools/podman
Release list
v5.8.7
Security
- This release addresses (CVE-2025-11395), where importing images containing crafted layer tarballs with the
podman loadcommand, or importing volumes containing crafted symlinks withpodman volume import, allows overwriting files on the host. - This release also addresses CVE-2026-79699 and CVE-2026-79705, though we do not believe these CVEs are exploitable through the Podman command line.
Misc
- Updated Buildah to v1.43.4
- Updated Common to v0.67.2
- Updated Image to v5.39.3
- Updated Storage to v1.62.1
v6.1.2
Security
- This release addresses (CVE-2025-11395), where importing images containing crafted layer tarballs with the
podman loadcommand, or importing volumes containing crafted symlinks withpodman volume import, allows overwriting files on the host. - This release also addresses CVE-2026-79699 and CVE-2026-79705, though we do not believe these CVEs are exploitable through the Podman command line.
Misc
- Updated Buildah to v1.45.1
- Updated Common to v0.69.2
- Updated Image to v5.41.2
- Updated Storage to v1.64.1
v6.1.1
Security
- This release addresses CVE-2026-17106, where a crafted tar archive could write outside the extraction directory through the use of malicious links (GHSA-hfg8-hc9c-6c3h).
Bugfixes
- Fixed broken rootlessport bind behavior with
-p 0.0.0.0:... -p [::]:...which failed instead of binding both v4 and v6 separately. Podman Machine on WSL should now correctly forward ports again by binding separate IPv4 and IPv6 sockets to make the WSL forwarder logic work again (#29377).
v5.8.6
Security
- This release addressed CVE-2026-19730 where the
podman quadlet install --replacecommand did not truncate the file being replaced, meaning replacing a longer file with a shorter one would result in content from the original file incorrectly being retained.
v6.1.0
Features
- A new command has been added,
podman volume rename, to allow renaming volumes. Volumes created using volume drivers and volumes that are currently used by a container cannot be renamed (#28189). - A new command has been added,
podman machine restart, to allow easy restart of VMs managed bypodman machine(#28366). - The
podman network rmcommand now includes a new option,--ignore, which suppresses errors when attempting to remove networks that do not exist (#28363). - The
podman manifest pushcommand now includes two new options,--retryand--retry-delay, which allow pushes to be automatically retried on failure (#28590). - Quadlet
.containerunits now support a new key,ImageVolume=, to configure how volumes from images are handled (#28875). - The
podman generate kubecommand now includes support for generating container healthchecks as alivenessProbe(#22095). - A new option,
force_port_listen, has been added tocontainers.conf. This is required to be set when running Podman on WSL to support port forwarding from the Windows host. It is automatically set on newly-createdpodman machineVMs on Windows using the WSL provider.
Changes
- The
podman infocommand now includes free memory available on the host (in addition to used memory and total memory) (#29116). - The Pesto rootless port forwarding tool now supports IPv6 port forwarding with source IP preservation.
Bugfixes
- Fixed a bug where the remote Podman client could hang on some operations when connecting to a remote Podman service over SSH (#28453).
- Fixed a bug where the
podman image scpcommand could not be used with usernames containing an@character (#27655). - Fixed a bug where the
podman kube playcommand did not properly validate requestedhostPortbindings, allowing the creation of containers with duplicated host ports which would never be able to start at the same time (#26622). - Fixed a bug where
podman machineVMs on Windows created using thehypervprovider would sometimes not properly start due to a race conditioning setting up volume mounts. - Fixed a bug where
podman machineVMs on Mac where machines could be left in an inconsistent state if thepodman machine startcommand was interrupted by a signal. - Fixed a bug where creating a container on a
podman machineVM on Mac that attempted to bind to a port number number 1024 would return a nonsensical error message; a clear error explaining that privileged ports cannot be bound is now returned. - Fixed a bug where the
podman quadlet listandpodman quadlet rmcommands did not function properly with uninstantiated template Quadlets. - Fixed a bug where the
podman quadlet installcommand would occasionally fail to install a Quadlet if non-quadlet files were specified. - Fixed a bug where the
podman quadlet installcommand would not refuse to install Quadlets including non-quadlet files if the--applicationoption was not specified. - Fixed a bug where healthcheck logs could be corrupted, preventing proper healthcheck operation, if a healthcheck was killed midway through writing the file.
- Fixed a bug where the
podman volume prune --allcommand incorrectly discarded label filters, causingpodman volume prune --all --filter label=footo prune all volumes, not just those with thefoolabel. - Fixed a bug where the
podman events --format=jsoncommand would printnullinstead of an error when the server sent an event that could not be decoded. - Fixed a bug where a race condition could cause Quadlet to generate corrupt systemd units (#29004).
- Fixed a bug where the
podman inspectcommand on a container with a single-element command (e.g.podman run fedora bash) would include the command in bothPathandArgs, when it should only have been included inPath(#29155). - Fixed a bug where the
--formatoption topodman inspecton containers did not properly support some format specifiers supported by Docker (e.g.{{.HostIp}}did not work, but{{.HostIP}}did) (#29164). - Fixed a bug where the Quadlet generator would not write error messages to
STDERRbut only to/dev/kmsg, meaning that errors were not visible fromsystemd-analyze --generators verifyand other tooling invoking the systemd generator directly. - Fixed a bug where containers which failed to start would, in some circumstances, not properly clean up, resulting in improper behavior (#26143).
- Fixed a bug where the
podman kube generatecommand would improperly generate warning messages only applicable when running as a rootless user on an SELinux enabled system when not running in that configuration (#17743).
API
- Fixed a bug where the Compat and Libpod Create endpoint for Exec Sessions (
/containers/$CID/exec) did not honor theConsoleSizeparameter in the exec config. - The Compat API has seen further changes to improve support for the Docker v1.44 API, including the deprecation of several fields removed in that release.
- Preparations have begun to implement support for the v1.45 API.
Misc
- Updated Buildah to v1.45.0
- Updated the image library to v5.41.1
- Updated the storage library to v1.64.0
- Updated the common library to v0.69.1
v6.1.0-RC1
Features
- A new command has been added,
podman volume rename, to allow renaming volumes. Volumes created using volume drivers and volumes that are currently used by a container cannot be renamed (#28189). - A new command has been added,
podman machine restart, to allow easy restart of VMs managed bypodman machine(#28366). - The
podman network rmcommand now includes a new option,--ignore, which suppresses errors when attempting to remove networks that do not exist (#28363). - The
podman manifest pushcommand now includes two new options,--retryand--retry-delay, which allow pushes to be automatically retried on failure (#28590). - Quadlet
.containerunits now support a new key,ImageVolume=, to configure how volumes from images are handled (#28875). - The
podman generate kubecommand now includes support for generating container healthchecks as alivenessProbe(#22095).
Changes
- The
podman infocommand now includes free memory available on the host (in addition to used memory and total memory) (#29116). - The Pesto rootless port forwarding tool now supports IPv6 port forwarding with source IP preservation.
Bugfixes
- Fixed a bug where the remote Podman client could hang on some operations when connecting to a remote Podman service over SSH (#28453).
- Fixed a bug where the
podman image scpcommand could not be used with usernames containing an@character (#27655). - Fixed a bug where the
podman kube playcommand did not properly validate requestedhostPortbindings, allowing the creation of containers with duplicated host ports which would never be able to start at the same time (#26622). - Fixed a bug where
podman machineVMs on Windows created using thehypervprovider would sometimes not properly start due to a race conditioning setting up volume mounts. - Fixed a bug where
podman machineVMs on Mac where machines could be left in an inconsistent state if thepodman machine startcommand was interrupted by a signal. - Fixed a bug where creating a container on a
podman machineVM on Mac that attempted to bind to a port number number 1024 would return a nonsensical error message; a clear error explaining that privileged ports cannot be bound is now returned. - Fixed a bug where the
podman quadlet listandpodman quadlet rmcommands did not function properly with uninstantiated template Quadlets. - Fixed a bug where the
podman quadlet installcommand would occasionally fail to install a Quadlet if non-quadlet files were specified. - Fixed a bug where the
podman quadlet installcommand would not refuse to install Quadlets including non-quadlet files if the--applicationoption was not specified. - Fixed a bug where healthcheck logs could be corrupted, preventing proper healthcheck operation, if a healthcheck was killed midway through writing the file.
- Fixed a bug where the
podman volume prune --allcommand incorrectly discarded label filters, causingpodman volume prune --all --filter label=footo prune all volumes, not just those with thefoolabel. - Fixed a bug where the
podman events --format=jsoncommand would printnullinstead of an error when the server sent an event that could not be decoded. - Fixed a bug where a race condition could cause Quadlet to generate corrupt systemd units (#29004).
- Fixed a bug where the
podman inspectcommand on a container with a single-element command (e.g.podman run fedora bash) would include the command in bothPathandArgs, when it should only have been included inPath(#29155). - Fixed a bug where the
--formatoption topodman inspecton containers did not properly support some format specifiers supported by Docker (e.g.{{.HostIp}}did not work, but{{.HostIP}}did) (#29164). - Fixed a bug where the Quadlet generator would not write error messages to
STDERRbut only to/dev/kmsg, meaning that errors were not visible fromsystemd-analyze --generators verifyand other tooling invoking the systemd generator directly. - Fixed a bug where containers which failed to start would, in some circumstances, not properly clean up, resulting in improper behavior (#26143).
- Fixed a bug where the
podman kube generatecommand would improperly generate warning messages only applicable when running as a rootless user on an SELinux enabled system when not running in that configuration (#17743).
API
- Fixed a bug where the Compat and Libpod Create endpoint for Exec Sessions (
/containers/$CID/exec) did not honor theConsoleSizeparameter in the exec config. - The Compat API has seen further changes to improve support for the Docker v1.44 API, including the deprecation of several fields removed in that release.
- Preparations have begun to implement support for the v1.45 API.
Misc
- Updated Buildah to v1.45.0
- Updated the image library to v5.41.0
- Updated the storage library to v1.64.0
- Updated the common library to v0.69.0
v6.0.2
Bugfixes
- Fixed a bug where
podman machineVMs created by the WSL provider on Windows were not properly cleaned up if thepodman machine initcommand failed (#27036). - Fixed a bug where the Windows installer for Podman would, when installing for all users, incorrectly modify the path of only the user installing Podman (#29160).
- Fixed a bug where the remote Podman client would throw errors when run on a Linux system that was not using Cgroups v2 (#29241).
Misc
- Updated Buildah to v1.44.1
v6.0.1
Bugfixes
- Fixed a bug where Podman Machine VMs on Mac using the
libkrunprovider could be regularly turned off by a port-scanning process on the host unintentionally commanding the VM to shut down. - Fixed a bug where the
podman machine initcommand would fail on Windows hosts when using thehypervprovider when WSL was not installed (#29053). - Fixed a bug where the
podman machine initcommand would fail on Windows hosts when using thewslprovider when the user was a Hyper-V admin but Hyper-V is disabled (#29138). - Fixed a bug where error messages from the OCI runtime were sometimes not displayed when
--log-level=debugwas passed to Podman. - Fixed a bug where the
podman machine os upgradecommand did not function properly (#29085). - Fixed a bug where the default image used by
podman machinewas not being properly cached (#29090). - Fixed a bug where rootful Podman Machine VMs on Windows using the
wslprovider would fail to start (#29003). - Fixed a bug where commands that did not support the
--replaceoption would incorrectly suggest using that option in error messages (#24537). - Fixed a bug where the Pesto rootless port forwarding tool (enabled by
rootless_port_forwarder=pasta) did not properly clean up rules on container restart and network reload, causing failures to forward traffic (#29032).
v5.8.5
Bugfixes
- Fixed a bug where Podman Machine VMs on Mac using the libkrun provider could be regularly turned off by a port-scanning process on the host unintentionally commanding the VM to shut down.
v5.8.4
Security
- This release addresses CVE-2026-57231, where a malicious image using malformed
Enventries could cause host environment variables to leak into containers run based on the image, including the ability to use the*glob operator to leak large numbers of environment variables without knowing their exact names (GHSA-4hq8-gpf5-8p68). - The golang.org/x/crypto library has been updated to v0.53.0, addressing CVE-2026-39830 and CVE-2026-42508.
Bugfixes
- Fixed a bug where the remote Podman client's
podman savecommand would fail on Linux when using the-f oci-diror-f docker-dirarguments.