CVE-2026-95839: containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor
containerd is an open-source container runtime. From 2.2.0 until 2.2.10, 2.3.7, and 2.4.2, image manifest processing through the transfer service can encounter a child descriptor containing the io.containerd.manifest.subject annotation and a malformed digest. Pulling or importing such an image, including through a default CRI PullImage request, can trigger an unrecovered panic and crash the containerd daemon. In Kubernetes, kubelet retries can repeatedly trigger the crash and disrupt container operations on the worker node. This issue is fixed in versions 2.2.10, 2.3.7, and 2.4.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.2.10 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.3.7 - Upgrade
Upgrade
containerdto a version that resolves this vulnerability.Fixed in 2.4.2
Event History
Frequently Asked Questions
Which deployments are exposed to this crash?
containerd versions from 2.2.0 up to, but not including, 2.2.10 are affected, as are versions before 2.3.7 in the 2.3 line and before 2.4.2 in the 2.4 line. Systems that pull or import images through containerd's transfer service are exposed; this includes default CRI PullImage requests.
What must an attacker control to trigger the issue?
An attacker needs to cause containerd to pull or import an image whose manifest processing reaches a child descriptor with the io.containerd.manifest.subject annotation and a malformed digest. Processing that descriptor can cause an unrecovered panic and terminate the containerd daemon.
What is the operational impact in Kubernetes?
Kubelet retries may repeatedly re-trigger the daemon crash when attempting to pull the malformed image. This can disrupt container operations on the affected worker node.
How can this be remediated?
Upgrade containerd to 2.2.10, 2.3.7, or 2.4.2, as appropriate for the deployed release line.