All vulnerabilities

Servers and applications

CVE-2026-53492

CDI annotation smuggling during CRI checkpoint restore

Severity
High 8.4
Published
18 Jun 2026
Last changed
2 Jul 2026
Added to UpHeron
1 Nov 2026
Fixed in
2.1.9, 2.2.5, 2.3.2
Exploit chance
0.4% in the next 30 daysHigher than 29% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Improper input validation (CWE-20)Incorrect authorization (CWE-863)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Change data
CVSS vector
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
Also known as
GHSA-33vj-92qq-66hc
Sources
NVD, Project advisories (GitHub)

Description

containerd's 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.

From containerd/containerd's security advisory.

Workarounds

Users can mitigate this issue by restricting the restoration of containers from untrusted checkpoint images. If Container Device Interface (CDI) capabilities are not utilized on the node, removing or temporarily relocating host CDI specifications from the default directories (/etc/cdi and /var/run/cdi) will eliminate the reachability of this vulnerability.

Workarounds as given by containerd/containerd's security advisory.

Affected software

SoftwareAffected versions
containerdServers and applications · cpe:a:linuxfoundation:containerd
  • From 2.1.0 before 2.1.9
  • From 2.2.0 before 2.2.5
  • From 2.3.0 before 2.3.2
containerdServers and applications · github:containerd/containerd
  • From 2.3.0 before 2.3.2

About containerd

container runtime

From Wikidata, CC0 1.0.
GitHub stars
21,483GitHub, 15 Nov 2026
Forks
4,206GitHub, 15 Nov 2026
Latest release
v2.4.2GitHub, 15 Nov 2026
Released
13 Oct 2026GitHub
Developer
Docker, Inc.Wikidata
License
Apache Software License 2.0Wikidata
Written in
GoWikidata
First published on GitHub
13 Nov 2015GitHub

Release lines

ReleaseLatestSecurity fixes
2.42.4.2Until 16 May 2027
2.3 (LTS)LTS2.3.7Until 30 Apr 2028
2.22.2.10Ended 6 Nov 2026
2.12.1.9Ended 3 Jul 2026
2.0 (LTS)LTS2.0.14Until 1 Mar 2027
1.7 (LTS)LTS1.7.36Ended 30 Sept 2026

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-53492
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-53492
  • GitHub Advisory Database https://github.com/advisories/GHSA-33vj-92qq-66hc
  • github.com https://github.com/containerd/containerd/security/advisories/GHSA-33vj-92qq-66hc