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
- 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.
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.
Affected software
| Software | Affected versions |
|---|---|
containerdServers and applications · cpe:a:linuxfoundation:containerd |
|
containerdServers and applications · github:containerd/containerd |
|
About containerd
container runtime
- 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
| Release | Latest | Security fixes |
|---|---|---|
| 2.4 | 2.4.2 | Until 16 May 2027 |
| 2.3 (LTS)LTS | 2.3.7 | Until 30 Apr 2028 |
| 2.2 | 2.2.10 | Ended 6 Nov 2026 |
| 2.1 | 2.1.9 | Ended 3 Jul 2026 |
| 2.0 (LTS)LTS | 2.0.14 | Until 1 Mar 2027 |
| 1.7 (LTS)LTS | 1.7.36 | Ended 30 Sept 2026 |
From endoflife.date.
Vulnerabilities in containerd
- In our list
- 33
- Published in the last 12 months
- 14
- Critical, last 12 months
- 1
- High, last 12 months
- 5
- Known exploited
- 0
- GHSA-8647-2jxj-p2rccontainerd: daemon crash when pulling an image with a crafted Content-Length headerMedium 13 Oct 2026
- CVE-2026-95839containerd: daemon crash when processing an image manifest with a malformed digestHigh 7.1 13 Oct 2026
- GHSA-hc94-p972-ch66containerd: host disk exhaustion when pulling an image with an unbounded layer streamMedium 13 Oct 2026
- GHSA-5p7c-hggf-c748containerd CRI plugin: mount and snapshot leak when container checkpoint restore failsMedium 13 Oct 2026
- CVE-2026-95837containerd CRI plugin: Checkpoint restore bypasses destination security contextHigh 7.8 12 Oct 2026
- CVE-2026-53493Image-pull DoS via crafted OCI index graph amplificationMedium 24 Sept 2026
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