Skip to main content
← All vulnerabilities
CVE-2026-50195GHSA-CVXM-645Q-P574GO-2026-5338

containerd: CRI checkpoint import allows local image tag poisoning

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 2.1.9, 2.2.5, 2.3.2
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • containerd containerd

    From 2.1.0 · fixed in 2.1.9; From 2.2.0 · fixed in 2.2.5; From 2.3.0 · fixed in 2.3.2

  • github.com/containerd/containerd/v2Go

    From 2.1.0 · fixed in 2.1.9

  • github.com/containerd/containerd/v2Go

    From 2.2.0 · fixed in 2.2.5

  • github.com/containerd/containerd/v2Go

    From 2.3.0 · fixed in 2.3.2

  • github.com/containerd/containerdGo

    All versions

  • github.com/containerd/containerd/v2Go

    From 2.1.0 · fixed in 2.1.9; From 2.2.0 · fixed in 2.2.5; From 2.3.0 · fixed in 2.3.2

References 1

GitHub · containerd/containerd