Skip to main content
Mallory
Unrated

Image Cache Poisoning via Unvalidated Checkpoint Image References in containerd CRI

IdentifiersCVE-2026-50195CWE-20

CVE-2026-50195 is a critical vulnerability in containerd's CRI checkpoint import process. During import or restore from a checkpoint image, containerd fails to validate the image references embedded in the checkpoint image configuration. An attacker who can create pods can supply a crafted checkpoint image that causes containerd to pull an attacker-controlled image and assign it an arbitrary local tag on the node. This poisons the node-local image cache by making a malicious image appear to be a legitimate cached image reference. On shared Kubernetes nodes, subsequent pods that rely on the poisoned local tag can start the attacker-controlled image instead of the intended one.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can poison the local image cache of a shared Kubernetes node and lead to cross-pod code execution. Pods scheduled later on the same node that use the affected image reference, particularly with pull policies such as IfNotPresent or Never, may execute the attacker-controlled image under the victim pod's identity and permissions. This can compromise workload isolation between pods on the same node and enable unauthorized execution in other tenants' or applications' contexts.

Mitigation

If you can’t patch tonight, do this now.

Disable containerd checkpoint/restore functionality where feasible, especially for untrusted checkpoint images. Do not import or restore checkpoints from untrusted sources. Restrict pod creation permissions to trusted principals, and reduce use of image pull policies such as IfNotPresent or Never on shared nodes where practical, since those policies increase the chance that a poisoned local cache entry will be reused. Upgrading remains the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade containerd to a fixed release. The vulnerability is fixed in containerd 2.3.2, 2.2.5, and 2.1.9. If running a vendor-managed or forked distribution, ensure the vendor has incorporated the upstream fix. Where untrusted checkpoints may already have been imported, review and remediate potentially poisoned node-local image caches and recreate affected workloads as appropriate.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
containerdContainerdapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.