CVE-2026-121885 · Runtime
NO FIX YET
Podman's auto-update reads service names from container image labels and restarts whatever units those labels name. A crafted image can make a host service restart, which can cause a denial of service and, when Podman runs with administrative privileges, can shut the host down.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Hosts that run Podman and use its auto-update feature on container images from sources that are not fully trusted, especially when Podman runs as root. Systems that do not use auto-update, or that only pull images they build and control, are unlikely to be exposed. The sources do not name fixed versions.
Not affected if no-auto-update, rootless-only, trusted-images-only
Who cares containers, linux, podman, self-hosted
podman --version and compare against the fixed release, if the sources give oneio.containers.autoupdate label) on hosts running podman auto-updateNo fix yet, per the sources.
A flaw was found in Podman. An attacker can trigger a Denial of Service (DoS) by supplying a container image containing crafted metadata labels. Podman's auto-update mechanism improperly trusts these image labels to determine which system services to restart. If a user runs the malicious container and auto-update processes it, arbitrary system services are restarted with the user's privileges, potentially allowing an attacker to shut down the host system when Podman runs with administrative privileges.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.