CVE-2026-53488: containerd CRI plugin: — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull
Impact A bug was found in containerd where the CRI plugin propagates labels from an image config (LABEL instruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via a plugin that consumes container labels for some operations.
Patches This bug has been fixed in the following containerd versions:
2.3.2 2.2.5 2.1.9 2.0.10 1.7.33
Users should update to these versions to resolve the issue.
Workarounds Ensure that only trusted images are used.
Credits The containerd project would like to thank Anthropic Research, in collaboration with Claude, the GKE Security Team using Gemini, and Robert Prast (@robertprast) for independently discovering and responsibly disclosing this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
Open an issue in containerd Email us at security@containerd.io
To report a security issue in containerd: Report a new vulnerability Email us at security@containerd.io
Other sources
containerd is an open-source container runtime. In versions prior to 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10 the CRI plugin propagates labels from an image config (LABEL instruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via a plugin that consumes container labels for some operations. This issue has been fixed in versions 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/containerd/containerd/v2to a version that resolves this vulnerability.Fixed in 2.3.2 - Upgrade
Upgrade
go/github.com/containerd/containerd/v2to a version that resolves this vulnerability.Fixed in 2.2.5 - Upgrade
Upgrade
go/github.com/containerd/containerd/v2to a version that resolves this vulnerability.Fixed in 2.1.9 - Upgrade
Upgrade
go/github.com/containerd/containerd/v2to a version that resolves this vulnerability.Fixed in 2.0.10 - Upgrade
Upgrade
go/github.com/containerd/containerdto a version that resolves this vulnerability.Fixed in 1.7.33 - Upgrade
Upgrade
debian/containerdto a version that resolves this vulnerability.Fixed in 2.1.9+ds1-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.7.33 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.3.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.2.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.1.9 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.0.10 - Compensating control
Ensure that only trusted images are used, since the CRI plugin propagates labels from an image config (Dockerfile LABEL) to a container without validation and this may result in executing an arbitrary command on the host via a plugin that consumes container labels for some operations.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53488?
CVE-2026-53488 has a critical severity rating of 9.4 according to the CVSS score.
What type of vulnerability is CVE-2026-53488?
CVE-2026-53488 is an input validation vulnerability in the containerd CRI plugin.
How does CVE-2026-53488 impact system security?
CVE-2026-53488 allows for command execution on the host due to unvalidated Docker image labels.
How do I fix CVE-2026-53488?
To mitigate CVE-2026-53488, ensure that you are using the latest version of containerd that addresses this vulnerability.
Which systems are affected by CVE-2026-53488?
CVE-2026-53488 affects the linuxfoundation Containerd software specifically.