Loading vulnerability…
CVE-2026-53492 is an improper access-control vulnerability in containerd's CRI checkpoint restore handling. Before versions 2.3.2, 2.2.5, and 2.1.9, the CRI implementation preserves Container Device Interface (CDI) annotations embedded in untrusted checkpoint image metadata rather than deriving CDI configuration exclusively from the pod's create-time specification. A user authorized to create pods can supply a crafted checkpoint whose CDI annotations request host-defined devices, causing arbitrary CDI edits, including device-node and host-mount injection, in the restored container and bypassing Kubernetes resource allocation and device-plugin enforcement.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A network-accessible vulnerability requiring low privileges and no user interaction. The supplied CVSS vectors indicate high confidentiality and integrity impacts, with no availability impact. The affected product and underlying flaw type are not specified.
A security bypass vulnerability in the Linux Container Runtime Interface (CRI).
A containerd vulnerability in CRI checkpoint restore that improperly trusts CDI annotations from untrusted checkpoint metadata, enabling bypass of Kubernetes resource allocation and device plugin enforcement during container restoration.
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.