chore(deps): update module github.com/containerd/containerd to v2 [security]#198
Open
alaudaa-renovate[bot] wants to merge 1 commit into
Open
Conversation
alaudaa-renovate
Bot
added
the
dependencies
Contributor
Author
ℹ Artifact update noticeFile name: artifact-scanner/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
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
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.
This PR contains the following updates:
v1.7.29->v2.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2026-46680
Impact
A bug was found in containerd where containers launched with a numeric
Userdirective that cannot be parsed as a 32-bit integer are incorrectly treated as a username. If a crafted image provides an/etc/passwdfile mapping this large numeric string to root, the container ultimately runs as root (UID 0). This allows the KubernetesrunAsNonRootrestriction 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:
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
runAsUserin the Kubernetes PodsecurityContextoverrides theUSERdirective in the image and prevents the bypass. Newer versions of Kubernetes, starting with 1.34, also appear to enforcerunAsNonRootproperly 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
For more information
If there are any questions or comments about this advisory:
To report a security issue in containerd:
containerd user ID handling bypass allows runAsNonRoot evasion
CVE-2026-46680 / GHSA-fqw6-gf59-qr4w
More information
Details
Impact
A bug was found in containerd where containers launched with a numeric
Userdirective that cannot be parsed as a 32-bit integer are incorrectly treated as a username. If a crafted image provides an/etc/passwdfile mapping this large numeric string to root, the container ultimately runs as root (UID 0). This allows the KubernetesrunAsNonRootrestriction 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:
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
runAsUserin the Kubernetes PodsecurityContextoverrides theUSERdirective in the image and prevents the bypass. Newer versions of Kubernetes, starting with 1.34, also appear to enforcerunAsNonRootproperly 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
For more information
If there are any questions or comments about this advisory:
To report a security issue in containerd:
Severity
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
containerd/containerd (github.com/containerd/containerd)
v2.0.0: containerd 2.0.0Compare Source
Welcome to the v2.0.0 release of containerd!
The first major release of containerd 2.x focuses on the continued stability of
containerd's core feature set with an easy upgrade from containerd 1.x. This
release includes the stabilization of new features added in the last 1.x release
as well as the removal of features which were deprecated in 1.x. The goal is to
support the vast community of containerd users well into the future along with
their ever increasing deployment footprints and variety of use cases.
See containerd 2.0 documentation for details on what is new and has changed in this release.
Highlights
LimitNOFILEfromcontainerd.service(#8924)aufssnapshotter (#8263)Build and Release Toolchain
cri-containerd-*.tar.gzrelease bundles (#9096)Container Runtime Interface (CRI)
Go client
Image Distribution
Runtime
io.containerd.runtime.v1.linuxandio.containerd.runc.v1(#8262)Security Advisories
Breaking
disable_cgroupfrom CRI config (#10594)LimitNOFILEfromcontainerd.service(#8924)io.containerd.runtime.v1.linuxandio.containerd.runc.v1(#8262)aufssnapshotter (#8263)Deprecations
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Dependency Changes
1f10f66->e8a1dd75330a85->2b5cbb2ea5083fnewd8f796aa7dc8b6newcca7078new3a7f492-> v1.1.0946c877->2e043c65d4384e78d3cae->78284952eb08e3-> v0.0.4686a1a2new432b235-> v0.9.0aacd6d4new90d013b-> v0.3.05fefd90new324edc3newa5ecb01->18e509bf223a00->bc3834cPrevious release can be found at v1.7.0
Which file should I download?
containerd-<VERSION>-<OS>-<ARCH>.tar.gz: ✅Recommended. Dynamically linked with glibc 2.31 (Ubuntu 20.04).containerd-static-<VERSION>-<OS>-<ARCH>.tar.gz: Statically linked. Expected to be used on non-glibc Linux distributions. Not position-independent.In addition to containerd, typically you will have to install runc
and CNI plugins from their official sites too.
See also the Getting Started documentation.
v1.7.31: containerd 1.7.31Compare Source
Welcome to the v1.7.31 release of containerd!
The thirty-first patch release for containerd 1.7 contains various fixes
and updates including a security patch.
Security Updates
Highlights
Container Runtime Interface (CRI)
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
37 commits
7d2662653Prepare release notes for v1.7.313f795c02aupdate github.com/moby/spdystream v0.5.17b1e1b17bupdate to Go 1.25.9, 1.26.2b673f2d42update golangci-lint to v2.9.0 with go1.26 supportd88d8513aremove windows/arm from cross builda763407b5Ignore warnings for golangci-lint bump03dcd8360ci: bump golangci from 6.5.2 to 7.0.0c08711218Update github.com/moby/spdystream v0.2.0->v0.5.0043548f6dSkip TestExportAndImportMultiLayer on s390xe99bd6050[release/1.7] update runc binary to v1.3.53a3103aafCODEOWNERS: mark Sam and Chris as owners for 1.79b4cfa271Ignore NOCHANGE error53e9e73f0ci: modprobe xt_comment on almalinux61c2733fdFix TOCTOU race bug in tar extractionf854c1890fix issue where cni del is never executed5c091d92eapparmor: explicitly set abi/3.0177ac10feintegration: Fix TestImageLoad() failure on CI56da43d0fupdate to go1.24.13, go1.25.75cb3cb9baci: bump go 1.24.12, 1.25.6b1fa03843fix: sanitize error before gRPC return to prevent credential leak in pod eventse2c93a42ccri: emit warning for concurrent CreateContainerDependency Changes
Previous release can be found at v1.7.30
v1.7.30: containerd 1.7.30Compare Source
Welcome to the v1.7.30 release of containerd!
The thirtieth patch release for containerd 1.7 contains various fixes
and updates.
Highlights
Container Runtime Interface (CRI)
Runtime
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
26 commits
3d0ca6d2ePrepare release notes for v1.7.300bc74f47ecri,nri: don't drop requested CDI devices silently.7db16b562script/setup/install-cni: install CNI plugins v1.9.0bca897b47go.mod: golang.org/x/crypto v0.45.037cbd2224CI: drop Go 1.23ee49d1747Update Go requirements in BUILDING145978224ci: bump Go 1.24.11, 1.25.53dbadfaa1ci: bump Go 1.24.10, 1.25.42bac971f0ci(release): set GO_VERSION in Dockerfile34b89a574runc: Update runc binary to v1.3.46e0dd8956ci: update CIFuzz actions to support Ubuntu 24.043eea2a4afbuild(deps): bump github.com/opencontainers/selinux1194f5128remove sha256-simdce2d3a67f.github: skip 5 critest cases in window CI pipeline65271ea89fix: redact all query parameters in CRI error logsDependency Changes
Previous release can be found at v1.7.29
Configuration
📅 Schedule: Branch creation - "" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.