CVE-2026-46680 in containerd
containerd is an open-source container runtime. In versions prior to 1.7.32, 2.0.9, 2.2.4 and 2.3.1, containers launched with a numeric User directive that cannot be parsed as a 32-bit integer are incorrectly treated as a username, leading to runAsNonRoot evasion. If a crafted image provides an /etc/passwd file mapping this large numeric string to root, the container ultimately runs as root (UID 0). This allows the Kubernetes runAsNonRoot restriction to be bypassed, causing unexpected behavior for environments that require containers to run as a non-root user. This issue has been fixed in versions 1.7.32, 2.0.9, 2.2.4 and 2.3.1.
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 before 1.7.32
- containerd before 2.0.9
- containerd before 2.2.4
- containerd before 2.3.1
Fixed versions
- containerd 1.7.32 or later
- containerd 2.0.9 or later
- containerd 2.2.4 or later
- containerd 2.3.1 or later
How to fix it
CVE-2026-46680 affects containerd. In simple terms, a user may get access or power they should not have. Update to containerd 1.7.32 or later; containerd 2.0.9 or later; containerd 2.2.4 or later; containerd 2.3.1 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 before 1.7.32; containerd before 2.0.9; containerd before 2.2.4; containerd before 2.3.1.
- Update to: containerd 1.7.32 or later; containerd 2.0.9 or later; containerd 2.2.4 or later; containerd 2.3.1 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 1.7.32 or later; containerd 2.0.9 or later; containerd 2.2.4 or later; containerd 2.3.1 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-46680?
Linux Foundation containerd versions listed as affected should be reviewed: containerd before 1.7.32, containerd before 2.0.9, containerd before 2.2.4, containerd before 2.3.1.
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.