containerd · containerd · published 2026-07-01
CVE-2026-53492containerd CRI checkpoint restore CDI annotation smuggling
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-53492 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 29% of all CVEs. This containerd vulnerability: CVSS 8.4 (v4.0). Fixed upstream in containerd 2.3.2, 2.2.5, 2.1.9, 2.0.10 (+1 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in containerd 2.3.2, 2.2.5, 2.1.9, 2.0.10, 1.7.33.
Patch events
Container runtimecontainerd
containerd security releases: 2.3.2, 2.2.5, 2.1.9, 2.0.10, 1.7.33
Upgrade to
2.3.22.2.52.1.92.0.101.7.33Why: Vendor security release for server software (most severe: CVE-2026-53488).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (30th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.4 (v4.0)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 | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- containerd containerd
>= 2.1.0, < 2.1.9(affected)>= 2.2.0, < 2.2.5(affected)>= 2.3.0, < 2.3.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.