Loading vulnerability…
CVE-2026-53489 is a high-severity vulnerability in containerd affecting versions prior to 2.3.2, 2.2.5, and 2.1.9. The flaw is in the CRI plugin’s checkpoint restore logic, which restores the container log path from a checkpoint image without validating whether the restored container.log path is a symlink. Because the symlink target is not properly checked, a crafted checkpoint can cause the runtime to follow the symlink and expose an arbitrary file from the host through normal log retrieval mechanisms such as kubectl logs. The issue is effectively a symlink-following path validation failure during checkpoint restore that results in unintended host file disclosure.
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.
9 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.