Containerd
containerd user ID handling bypass allows runAsNonRoot evasion
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.7.32
- >= 2.0.4, < 2.0.9
- >= 2.0.10, < 2.2.4
- >= 2.2.5, < 2.3.1
Fixed in 1.7.32, 2.0.9, 2.2.4, 2.3.1
Mitigation
Upgrade containerd to 1.7.32 or 2.0.9 or 2.2.4 or 2.3.1 or later.
References
- Vendor advisory github.com/containerd/containerd/security/advi…
Timeline
Days relative to CVE publicationFirst public PoC 41 days before publication; not in CISA KEV. First PoC: r0binak/CVE-2026-46680 (created 21 May 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| r0binak/CVE-2026-46680 | 21 May 2026 −41 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.