chore(deps): update module github.com/containerd/containerd/v2 to v2.0.9 [security] (main)#45
Open
anaconda-renovate[bot] wants to merge 1 commit into
Conversation
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
8f427fb to
07f2cea
Compare
Author
ℹ️ Artifact update noticeFile name: 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:
v2.0.5→v2.0.9containerd CRI server: Host memory exhaustion through Attach goroutine leak
CVE-2025-64329 / GHSA-m6hq-p25p-ffr2 / GO-2025-4108
More information
Details
Impact
A bug was found in containerd's CRI Attach implementation where a user can exhaust memory on the host due to goroutine leaks.
Repetitive calls of CRI Attach (e.g.,
kubectl attach) could increase the memory usage of containerd.Patches
This bug has been fixed in the following containerd versions:
Users should update to these versions to resolve the issue.
Workarounds
Set up an admission controller to control accesses to
pods/attachresources.e.g., Validating Admission Policy.
Credits
The containerd project would like to thank @Wheat2018 for responsibly disclosing this issue in accordance with the containerd security policy.
References
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-64329
For more information
If you have any questions or comments about this advisory:
To report a security issue in containerd:
Severity
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
containerd affected by a local privilege escalation via wide permissions on CRI directory
CVE-2024-25621 / GHSA-pwhc-rpq9-4c8w / GO-2025-4100
More information
Details
Impact
An overly broad default permission vulnerability was found in containerd.
/var/lib/containerdwas created with the permission bits 0o711, while it should be created with 0o700/run/containerd/io.containerd.grpc.v1.criwas created with 0o755, while it should be created with 0o700/run/containerd/io.containerd.sandbox.controller.v1.shimwas created with 0o711, while it should be created with 0o700The directory paths may differ depending on the daemon configuration.
When the
tempdirectory path is specified in the daemon configuration, that directory was also created with 0o711, while it should be created with 0o700.Patches
This bug has been fixed in the following containerd versions:
Users should update to these versions to resolve the issue.
These updates automatically change the permissions of the existing directories.
Workarounds
The system administrator on the host can manually chmod the directories to not
have group or world accessible permisisons:
An alternative mitigation would be to run containerd in rootless mode.
Credits
The containerd project would like to thank David Leadbeater for responsibly disclosing this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
To report a security issue in containerd:
Severity
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
containerd affected by a local privilege escalation via wide permissions on CRI directory in github.com/containerd/containerd
CVE-2024-25621 / GHSA-pwhc-rpq9-4c8w / GO-2025-4100
More information
Details
containerd affected by a local privilege escalation via wide permissions on CRI directory in github.com/containerd/containerd
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
containerd CRI server: Host memory exhaustion through Attach goroutine leak in github.com/containerd/containerd
CVE-2025-64329 / GHSA-m6hq-p25p-ffr2 / GO-2025-4108
More information
Details
containerd CRI server: Host memory exhaustion through Attach goroutine leak in github.com/containerd/containerd
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
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)
v2.0.9: containerd 2.0.9Compare Source
Welcome to the v2.0.9 release of containerd!
The ninth patch release for containerd 2.0 includes various bug fixes and updates, including a security fix.
containerd
Ensure container exit events are not lost during containerd restart (#11633)
Apply hardening to avoid TOCTOU race in tar extraction (#13237)
Fix handling of out-of-range USER values in OCI spec to avoid unexpected username/group lookups (#13449)
Apply hardening to block AF_ALG in default socket policy (#13407)
Support both "volatile" and "fsync=volatile" mount options for volatile snapshotter (#13298)
Fix bugs in sandbox service affecting sandbox creation configuration and event publishing (#13271)
Set AppArmor abi conditionally to support versions < 3.0 (#13277)
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
18 commits
2da65b8bdPrepare release notes for v2.0.91a3d1c85eoci: return explicit error for out-of-range USER valuesfa2a97505seccomp: Block AF_ALG in default socket policy4b2b07879seccomp: Document socket rule scope and socketcall limitationea56c9605Support both styles of volatile mount option3d34dc820sandbox: forward Create fields, fix event topics4b260843eapparmor: Set abi conditionally3e9c4d1e0Add GitHub Action for k8s node e2e testscf73e6873Fix TOCTOU race bug in tar extraction2320b319ecri:fix lost container exit events if they arrive before info is cachedThis release has no dependency changes
Previous release can be found at v2.0.8
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.
v2.0.8: containerd 2.0.8Compare Source
Welcome to the v2.0.8 release of containerd!
The eighth patch release for containerd 2.0 includes various bug fixes and updates, including a security fix.
Security 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
32 commits
c07b94f19Prepare release notes for v2.0.8 (missed line)c54b69f1aPrepare release notes for v2.0.8fde1480dfupdate github.com/moby/spdystream v0.5.15b2eee8a2update to Go 1.25.9, 1.26.2c579db16eupdate golangci-lint to v2.9.0 with go1.26 support185ddcfd0remove windows/arm from cross build8538158dfIgnore warnings for golangci-lint bump1cff32695ci: bump golangci from 6.5.2 to 7.0.02e02b8bb3Skip github.com/cyphar/filepath-securejoin license checkse71fc560bUpdating selinux to v1.13.1868869eb9fix: sanitize error before gRPC return to prevent credential leak in pod events40632e4f2fix: redact all query parameters in CRI error logs85c3b2b02CODEOWNERS: mark Sam and Chris as owners for 2.0902d804c9Update github.com/moby/spdystream v0.4.0->v0.5.0e92d7b131make linter happy in release12fc0e6caadd integration test for cni result nil8d912c6a2address comment742f8b8f6fix issue where cni del is never executedf24653597Ignore NOCHANGE error9c656fab4ci: update CIFuzz actions to support Ubuntu 24.04c71c4a091integration: Fix TestImageLoad() failure on CIbfee29999ci: modprobe xt_comment on almalinuxDependency Changes
Previous release can be found at v2.0.7
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.
v2.0.7: containerd 2.0.7Compare Source
Welcome to the v2.0.7 release of containerd!
The seventh patch release for containerd 2.0 includes various bug fixes and updates.
Security Updates
containerd
runc
Highlights
Container Runtime Interface (CRI)
Image Distribution
Runtime
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
56 commits
4931e24f1Prepare release notes for v2.0.7205bc4f2dUpdate mailmap5f708b76aMerge commit from fork8cd112d82Fix directory permissions05290b5bcMerge commit from fork4d1edf4adfix goroutine leak of container Attachb46dc6a67runc: Update runc binary to v1.3.35e9c82178Update GHA runners to use latest images for basic binaries build7f59248dcUpdate GHA runners to use latest image for most jobse1373e8a8ci: bump Go 1.24.9, 1.25.3e1a910a6aci: bump Go 1.24.8; 1.25.2fd04b7f17move exclude-dirs to issues.exclude-dirsb49377975update golangci-lint to v1.64.26e45022a1build(deps): bump golangci/golangci-lint-action from 6.3.2 to 6.5.009ce0f2a1build(deps): bump golangci/golangci-lint-action from 6.2.0 to 6.3.2de63a740bbuild(deps): bump golangci/golangci-lint-action from 6.1.1 to 6.2.0f953ee8a3bugfix:fix container logs lost because io close too quicklyf6f15f513CI: update Fedora to 432a2329cbdcri/server/podsandbox: disable event subscriberdfb954743CI: skip ubuntu-24.04-arm on private reposf6b02f6bbRemove additional fuzzers from CI75c13ee3frunc:Update runc binary to v1.3.1427cdd06cadd SystemdCgroup to default runtime options0b35e19fbinstall-runhcs-shim: fetch target commit instead of tags3212afc2fintegration: Add test for directives with usernsb855c6e10cri: Fix userns with Dockerfile VOLUME mounts that need copy05c0c99f4core/mount: Retry unmounting idmapped directoriesafdede4cecore/mount: Test cleanup of DoPrepareIDMappedOverlay()47205f814core/mount: Properly cleanup on doPrepareIDMappedOverlay errors6f4abd970core/mount: Don't call nil function on errorsa2f0d65d7core/mount: Only idmap once per overlayfs, not per layer1c32accd7Make ovl idmap mounts read-only9e72e91e6ci: bump Go 1.23.12, 1.24.6009622e04fix: create bootstrap.json with 0644 permission5bec0a332sys: fix pidfd leak in UnshareAfterEnterUserns2a2488131Fix intermittent test failures on Windows CIs018470948Remove WS2025 from CIs due to regressionb50cbbc98Add dial timeout field to hosts toml configurationDependency Changes
This release has no dependency changes
Previous release can be found at v2.0.6
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.
v2.0.6: containerd 2.0.6Compare Source
Welcome to the v2.0.6 release of containerd!
The sixth patch release for containerd 2.0 includes various bug fixes and updates.
Highlights
Container Runtime Interface (CRI)
Go client
Image Distribution
Runtime
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
49 commits
d94b0fee6Prepare release notes for v2.0.6f901e3c81ci: bump Go 1.23.11, 1.24.57e4ac4761go.mod: golang.org/x/* latestbed6d1401client/New: Don't unlazy the gRPC connection implicitly8094fa21acri:fix containerd panic when can't find sandbox extension552f717bebugfix:close container io when runtime create failedc4394d05aFix the panic caused by the failure of RunPodSandbox54f923a30ci: bump golang [1.23.10, 1.24.4] in build and release2de777dfeci: bump golang [1.23.9, 1.24.3] in build and release9724cd5eaEnable CIs to run on WS2022 and WS20257fc3151fc*: properly shutdown non-groupable shims to prevent resource leaks4396336a1core/runtime: should invoke shim binary10bcc6929Revert "not set sandbox id when use podsandbox type"f38eb62b6integration: add testcase to recover ungroupable shim2358561d5Update release upgrade tests to test 1.7 and 2.08931b1464Fix upgrade test runtime configfc9235910Fetch image with default platform only in TestExportAndImportMultiLayerf8679737estore extension when create sandbox in storecbfa66223fix(docker pusher): if authorizing a cross-repo mount fails, fall back7bf4d0a40.github: do not mark 2.0 releases as latestfa5a08244Update runc binary to v1.3.07cf3c604efix unbound SKIP_TEST variable error827be7c9dRevert "disable portmap test in ubuntu-22 to make CI happy"626a57dd7fix: update containerd config dump to reflect plugin config migrations.983dd336fcore/transfer/local: should not mark complete if it's not foundd2a30ea0cRevert criserver metrics subsystem back to crie9804ee0enot set sandbox id when use podsandbox type9ddeff7f7Fix vagrant setupDependency Changes
aacd6d4->6ae5c78Previous release can be found at v2.0.5
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.
Configuration
📅 Schedule: (UTC)
🚦 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 Mend Renovate.