CVEvulnerability

CVE-2026-53492

8.4 HIGH Published 2026-07-01 Modified 2026-07-02 Official page ↗
Status
Analyzed
Published
2026-07-01
Last modified
2026-07-02
Assigner
[email protected]
CVSS 4.0 ([email protected])
8.4 HIGH — CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/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
CVSS 3.1 ([email protected])
9.6 CRITICAL — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Weaknesses
CWE-20, CWE-863

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.

Affected configurations

• linuxfoundation containerd (>= 2.1.0 < 2.1.9) • linuxfoundation containerd (>= 2.2.0 < 2.2.5) • linuxfoundation containerd (>= 2.3.0 < 2.3.2)

Related

Weakness · CWE (2)

  • CWE-20 Improper Input Validation weakness
  • CWE-863 Incorrect Authorization weakness

References