CVE-2026-46680: containerd user ID handling bypass allows runAsNonRoot evasion
Impact A bug was found in containerd where containers launched with a numeric User directive that cannot be parsed as a 32-bit integer are incorrectly treated as a username. If a crafted image provides an /etc/passwd file mapping this large numeric string to root, the container ultimately runs as root (UID 0).
Published May 21, 2026 · Updated Jul 21, 2026
Affected packages
github.com/containerd/containerd
- Ecosystem
- Go
- Affected
- >= 1.7.27, < 1.7.32
- Fixed in
- 1.7.32
- Check
go list -m github.com/containerd/containerd
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.0.4, < 2.0.9
- Fixed in
- 2.0.9
- Check
go list -m github.com/containerd/containerd/v2
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.1.0-beta.0, < 2.2.4
- Fixed in
- 2.2.4
- Check
go list -m github.com/containerd/containerd/v2
github.com/containerd/containerd/v2
- Ecosystem
- Go
- Affected
- >= 2.3.0-beta.0, < 2.3.1
- Fixed in
- 2.3.1
- Check
go list -m github.com/containerd/containerd/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A bug was found in containerd where containers launched with a numeric User directive that cannot be parsed as a 32-bit integer are incorrectly treated as a username. 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.
Patches
This bug has been fixed in the following containerd versions:
- 2.3.1
- 2.2.4
- 2.0.9
- 1.7.32
Note: The containerd 2.1 release has reached its end of life and a fixed version is not provided.
Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used and that only trusted users have permissions to import images. Alternatively, enforcing a specific numeric runAsUser in the Kubernetes Pod securityContext overrides the USER directive in the image and prevents the bypass. Newer versions of Kubernetes, starting with 1.34, also appear to enforce runAsNonRoot properly regardless of this bug.
Credits
The containerd project would like to thank Lei Wang (@ssst0n3) for responsibly disclosing this issue in accordance with the containerd security policy.
Resources
- https://github.com/advisories/GHSA-265r-hfxg-fhmg (CVE-2024-40635)
For more information
If there are any questions or comments about this advisory:
- Open an issue in containerd
- Send an email to [[email protected]](mailto:[email protected])
To report a security issue in containerd:
- Report a new vulnerability
- Send an email to [[email protected]](mailto:[email protected])
Credited to ssst0n3.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-95839
containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor
high7.1Nov 19, 2026CVE-2026-95837
containerd CRI plugin: Checkpoint restore bypasses destination security context
high7.8Oct 15, 2026CVE-2026-95838
containerd: Unpack DoS via repeated opaque whiteouts
medium4.6Oct 15, 2026CVE-2026-53493
Containerd has image-pull DoS via crafted OCI index graph amplification
medium6.9Sep 25, 2026CVE-2026-53495
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service
medium6.8Sep 9, 2026CVE-2026-47262
containerd image-triggered runtime DoS via unbounded group parsing
medium6.9Jun 19, 2026
