CVE-2026-95839

7.1High

Published 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.1CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
Low
User action
None
Impact
High impact on availability
Weakness
CWE-248

What an attacker gets

Authenticated attackers can crash the containerd daemon by pulling a malicious image. This causes a denial of service on the worker node as Kubernetes repeatedly attempts to pull the image.

Root cause

The transfer service encounters an unrecovered panic when processing a child descriptor with a malformed digest and specific annotation.

Affected versions

containerd versions 2.2.0 through 2.2.9, 2.3.0 through 2.3.6, and 2.4.0 through 2.4.1.

CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Upgrade to containerd 2.2.10, 2.3.7, or 2.4.2. If you cannot patch immediately, restrict image pull access to trusted registries to prevent the processing of malicious manifests.

remediation — bash
$ containerd --version

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-95839