CVE-2026-53492 in containerd
containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.
Quick answer
Linux Foundation containerd should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- containerd 2.1.0 through versions before 2.1.9
- containerd 2.2.0 through versions before 2.2.5
- containerd 2.3.0 through versions before 2.3.2
Fixed versions
- containerd 2.1.9 or later
- containerd 2.2.5 or later
- containerd 2.3.2 or later
How to fix it
CVE-2026-53492 affects containerd. In simple terms, private data may be shown to someone who should not see it. Update to containerd 2.1.9 or later; containerd 2.2.5 or later; containerd 2.3.2 or later. If you cannot update today, limit who can reach this system until the fix is done.
- Find every place where containerd is installed or used.
- Check if the version matches: containerd 2.1.0 through versions before 2.1.9; containerd 2.2.0 through versions before 2.2.5; containerd 2.3.0 through versions before 2.3.2.
- Update to: containerd 2.1.9 or later; containerd 2.2.5 or later; containerd 2.3.2 or later.
- If you cannot update now, allow only trusted users and trusted networks.
- Check logs for crashes, strange requests, failed logins, or unexpected access.
- Change secrets or passwords if you think data may have been exposed.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is now: containerd 2.1.9 or later; containerd 2.2.5 or later; containerd 2.3.2 or later.
- Confirm the risky feature is no longer exposed to untrusted users.
- Run the affected workflow again and make sure it still works.
- Review logs again after the update.
- Run a new Fixnx scan if this software is part of a public website.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-53492?
Linux Foundation containerd versions listed as affected should be reviewed: containerd 2.1.0 through versions before 2.1.9, containerd 2.2.0 through versions before 2.2.5, containerd 2.3.0 through versions before 2.3.2.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.