containerd · containerd · published 2026-07-01
CVE-2026-50195containerd: CRI checkpoint import allows local image tag poisoning
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-50195 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 23% of all CVEs. This containerd vulnerability: CVSS 5.6 (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.3% (24th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.6 (v4.0)CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:L | 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. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the CRI checkpoint import process where it fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force containerd to pull a malicious image and assign it an arbitrary local tag, thereby poisoning the node's local image cache. Subsequently, if other pods on the same node attempt to use the poisoned tag with an IfNotPresent (or Never) pull policy, they will unknowingly execute the attacker's malicious image instead of the legitimate one. This can lead to a compromise of the affected pods, allowing the attacker to execute arbitrary code under the victim pod's identity. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.
Quoted from the CVE Program record.