CVE-2026-95839: containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor

Published Nov 16, 2026
·
Updated

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

1 affected component
containerd containerd>=2.2.0<2.2.10, >=2.3.0<2.3.7, >=2.4.0<2.4.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade containerd to a version that resolves this vulnerability.

    Fixed in 2.2.10
  2. Upgrade

    Upgrade containerd to a version that resolves this vulnerability.

    Fixed in 2.3.7
  3. Upgrade

    Upgrade containerd to a version that resolves this vulnerability.

    Fixed in 2.4.2

Event History

Nov 16, 2026
CVE Published
via MITRE·08:03 PM
Data Sourced
via MITRE·08:03 PM
DescriptionWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203