Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Unrated

containerd CRI image label propagation host command execution

IdentifiersCVE-2026-53488CWE-20

containerd contains a vulnerability in its CRI plugin where labels from an image configuration (for example, LABEL instructions in a Dockerfile) are propagated to container labels without sanitization or validation. A crafted container image can therefore inject attacker-controlled label values into the resulting container metadata. If a downstream component or plugin consumes those container labels for operational behavior, this can lead to arbitrary command execution on the host. Reported examples include label-consuming plugins such as the restart-monitor binary:// logger. The issue does not require checkpoint/restore to be enabled.

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 result in arbitrary command execution on the host, potentially with host-root privileges, triggered by pulling or running a maliciously crafted container image whose image-config labels are propagated by containerd CRI into container labels consumed by host-side plugins. This creates a path from untrusted image metadata to host-level execution and can enable full node compromise and cross-workload impact on shared Kubernetes nodes.

Mitigation

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

There is no complete workaround short of upgrading to a patched version. Until patching is complete, restrict workloads to trusted images only and reduce or disable use of host-side plugins or integrations that consume container labels for command execution or other sensitive operations where feasible.

Remediation

Patch, then assume compromise.

Upgrade containerd to a fixed release. Reported fixed versions are 1.7.33, 2.0.10, 2.1.9, 2.2.5, and 2.3.2, depending on the deployed branch. Any forked or derivative implementations should incorporate the upstream fix that stops propagating unvalidated image-config labels into container labels used by plugins.
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

5 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 activity4

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