containerd · containerd · published 2026-07-01
CVE-2026-53488containerd CRI plugin: — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-53488 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 7% of all CVEs. This containerd vulnerability: CVSS 9.4 (v4.0), a successful attack gives total control of the component. 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.2% (7th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.4 (v4.0)CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- containerd containerd
< 1.7.33(affected)>= 2.0.0, < 2.0.10(affected)>= 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 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10 the CRI plugin propagates labels from an image config (LABEL instruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via a plugin that consumes container labels for some operations. This issue has been fixed in versions 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10.
Quoted from the CVE Program record.