CVE-2026-53488 affects containerd's CRI plugin. In containerd versions prior to 1.7.33, 2.3.2, 2.2.5, 2.1.9, and 2.0.10, labels from an image configuration, specifically values set via the Dockerfile LABEL instruction, are propagated to container labels without validation or sanitization. Because downstream components or plugins may consume container labels for operational behavior, a crafted image can supply malicious label values that are later interpreted by such a plugin. The provided context specifically identifies the restart-monitor binary:// logger path as an example sink, where image-config LABEL data can flow into plugin behavior and result in arbitrary command execution on the host.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.