CVE-2026-53492

Description

containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

CVSS Metrics

• v4.0•HIGH•Score: 8.4CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N

EPSS Trends

Current EPSS score: 0.41%• Percentile: 33%

Techniques & Countermeasures

• CWE-20•Improper Input Validation

  The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

• CWE-863•Incorrect Authorization

  The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Affected Systems

• containerd•containerd

  ≥ 2.1.0, < 2.1.9 | ≥ 2.2.0, < 2.2.5 | ≥ 2.3.0, < 2.3.2

• github.com/containerd•containerd

  all

• github.com/containerd/containerd•v2

  ≥ 2.1.0, < 2.1.9 | ≥ 2.2.0, < 2.2.5 | ≥ 2.3.0, < 2.3.2

References (2)

• https://github.com/containerd/containerd/security/advisories/GHSA-33vj-92qq-66hc
• https://github.com/containerd/containerd