bump containerd to v2.2.4 (CVE-2026-46680)#4217
Open
eriknordmark wants to merge 1 commit into
Open
Conversation
containerd v2.2.0 (currently pinned in tools/containerd-dev) is vulnerable to CVE-2026-46680: when an image's User directive is a numeric string outside int32 range, containerd treats it as a username and resolves it against the image's /etc/passwd, letting a crafted image escape Kubernetes runAsNonRoot enforcement. Fixed on the 2.2 line in v2.2.4. The bump cascades through the FROM in pkg/containerd, pkg/init and test/pkg/containerd (all of which build off linuxkit/containerd-dev) and the example/test/project YAMLs that pin the resulting tree hashes. CI on this PR will fail until a maintainer pushes the rebuilt linuxkit/containerd-dev image; I don't have push access to the linuxkit/ Docker Hub org. Signed-off-by: eriknordmark <erik@zededa.com> Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
- What I did
Bumped containerd from v2.2.0 to v2.2.4 in
tools/containerd-dev/Dockerfile. This fixes CVE-2026-46680: an image whoseUserdirective is a numeric string outside int32 range (e.g."9999999999") is treated as a username and resolved against the image's/etc/passwd. A crafted/etc/passwdmapping the same string to UID 0 then makes the container run as root, defeating KubernetesrunAsNonRoot. Fixed on the 2.2 line in v2.2.4.- How I did it
tools/containerd-dev/Dockerfile:CONTAINERD_COMMIT=v2.2.0→v2.2.4.FROM linuxkit/containerd-dev:<hash>line inpkg/containerd/Dockerfile,pkg/init/Dockerfile, andtest/pkg/containerd/Dockerfile(the three consumers called out by the comment intools/containerd-dev/Dockerfile).linuxkit/containerd:<hash>,linuxkit/init:<hash>, andlinuxkit/test-containerd:<hash>tree hashes to the new values.Mirrors the scope of the v2.2.0 bump (
2dd12173, 2025-11-18).- How to verify it
make -C pkg buildwill fail on this PR until the newlinuxkit/containerd-dev:405449f30ba384a0f67ad1b75f78a501604f2e44image is published to Docker Hub. I don't have push access to thelinuxkit/org, so a maintainer needs to build & push that image (and the dependentlinuxkit/containerd,linuxkit/init,linuxkit/test-containerdtags) before CI can resolve the FROMs. Once the dev image is on Hub, CI should run cleanly.- Description for the changelog
Update containerd to v2.2.4 (fixes CVE-2026-46680).