Repository navigation
Update module github.com/containerd/containerd/v2 to v2.3.7 [SECURITY] (release-v0.9) - #3705
Conversation
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
|
🤖 Finished Review · ✅ Success · Started 5:45 AM UTC · Completed 5:54 AM UTC Commit: Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.56 |
|
Risk Assessment: moderate (2/5) DetailsBot-authored security patch updating containerd v2 dependency across 2 files and 8 lines; Tier 1 signals unchanged from prior assessment; dependency file count elevates Tier 1 slightly but minimal blast radius and bot authorship keep overall risk moderate. Previous runRisk Assessment: moderate (2/5) DetailsBot-authored security patch updating containerd v2 dependency across only 2 files and 8 lines; dependency file count elevates Tier 1 but minimal blast radius and bot authorship keep overall risk moderate. Previous run (2)Risk Assessment: moderate (2/5) DetailsSmall, bot-authored security dependency update (go.mod/go.sum only, 8 lines changed) with no source or CI changes; moderate score driven by dependency file changes and mild churn/multi-author activity in those files within 90 days. |
|
Looks good to me Labels: Renovate bot security dependency update modifying Go dependency files. Previous run<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOltdfQ== --> Looks good to me Previous run (2)ReviewReason: tool-failure This PR was NOT reviewed. Do not count this as an approval. Previous run (3)<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOltdfQ== --> Looks good to me Labels: Go dependency security update touching go.mod and go.sum. |
e970982 to
8f8906f
Compare
|
🤖 Finished Review · ❌ Failure (post-script /home/runner/work/cli/cli/.fullsend/.fullsend-cache/resources/sha256/3b4860c748ffd59d27bac1cb5f7f8ca71c8d3b3daba0bbfb012969f8c5127f50/scripts/post-review.sh failed: exit status 1) · Started 2:54 PM UTC · Completed 3:05 PM UTC Commit: Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.41 |
8f8906f to
a0be785
Compare
|
🤖 Finished Review · ✅ Success · Started 1:59 AM UTC · Completed 2:08 AM UTC Commit: Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.93 |
Superseded by updated review
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
a0be785 to
faf7fdb
Compare
|
🤖 Finished Review · ✅ Success · Started 4:02 AM UTC · Completed 4:14 AM UTC Commit: Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.10 |
Superseded by updated review
This PR contains the following updates:
v2.3.4→v2.3.7containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service
CVE-2026-53495 / GHSA-7jxh-36q5-gcqv / GO-2026-6444
More information
Details
Impact
A bug in containerd's CRI ExecSync implementation allows exec probes and lifecycle hooks with background child processes to keep containerd's stdio-drain goroutines indefinitely blocked. Because the I/O drain phase lacks a default timeout or context cancellation handling, repeated ExecSync invocations (like probes) that include long-lived background processes against a container can cause containerd to leak goroutines and host memory. Over time, this resource exhaustion can cause the containerd daemon to be terminated by the OOM killer, rendering containerd unavailable until it is restarted. This issue affects containerd on Linux systems running with the CRI plugin enabled. Users not using containerd's CRI implementation or not running containers on Linux are not affected.
Patches
This bug has been fixed in containerd 2.3.5, 2.2.8, 2.0.12, and 1.7.35. Users should update to these versions to resolve the issue.
Workarounds
Ensure exec probes and lifecycle hooks do not launch long-lived background child processes.
Credits
The containerd project would like to thank XlabAI Team of Tencent Xuanwu Lab (xlabai@tencent.com), including Guannan Wang, Zhanpeng Liu, Jiashuo Liang, and Guancheng Li, and @IamwhatIamSY who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
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:N/PR:L/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: Unpack DoS via repeated opaque whiteouts
CVE-2026-95838 / GHSA-rp3h-jf77-q9p4 / GO-2026-6796
More information
Details
Impact
A vulnerability exists in containerd's layer unpack handler where the processing of certain image layers causes superlinear time complexity. During the unpack operation, specific file configurations within the layer can trigger repeated directory traversals.
Consequently, pulling or importing a maliciously crafted image can result in increased unpack times and a moderate increase in CPU usage. This delays container startup, even if the compressed image layers are small. Additionally, in orchestrators like Kubernetes that apply concurrency limits to image pulls, these excessively long operations can reduce the available concurrency for other pulls, potentially delaying unrelated container deployments.
Patches
This bug has been fixed in containerd 2.3.5, 2.2.8, 2.0.12, and 1.7.35. Users should update to these versions to resolve the issue.
Workarounds
There are no known workarounds for this issue. Users are advised to only pull and import trusted images from known registries until the patch can be applied.
Credits
The containerd project would like to thank Jakub Ciolek of AlphaSense 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:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service in github.com/containerd/containerd
CVE-2026-53495 / GHSA-7jxh-36q5-gcqv / GO-2026-6444
More information
Details
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service in github.com/containerd/containerd
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
containerd: Unpack DoS via repeated opaque whiteouts in github.com/containerd/containerd
CVE-2026-95838 / GHSA-rp3h-jf77-q9p4 / GO-2026-6796
More information
Details
containerd: Unpack DoS via repeated opaque whiteouts in github.com/containerd/containerd
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Containerd has image-pull DoS via crafted OCI index graph amplification
CVE-2026-53493 / GHSA-pg57-6jwg-q645 / GO-2026-6597
More information
Details
Impact
A vulnerability exists in containerd's image pull handlers where a crafted OCI image index containing deeply nested or heavily fanned-out descriptor graphs can cause unbounded CPU and memory consumption. During the
PullImageoperation, the recursive traversal and processing of child descriptors lack sufficient depth and breadth limits, and fail to adequately deduplicate identical descriptors. This unbounded traversal leads to excessive resource allocation.Consequently, pulling a malicious image reference can result in prolonged stalls during container creation and significant resource pressure on the host system. This issue occurs entirely during the image pull phase, prior to any container execution.
Patches
This bug has been fixed in containerd 2.4.1, 2.3.6, 2.2.9, 2.0.13, and 1.7.36. Users should update to these versions to resolve the issue.
Workarounds
There are no known workarounds for this issue. Users are advised to only pull trusted images from known registries until the patch can be applied.
Credits
The containerd project would like to thank Jakub Ciolek at ElevenLabs and @jlgore who independently discovered and responsibly disclosed 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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Containerd has image-pull DoS via crafted OCI index graph amplification in github.com/containerd/containerd
CVE-2026-53493 / GHSA-pg57-6jwg-q645 / GO-2026-6597
More information
Details
Containerd has image-pull DoS via crafted OCI index graph amplification in github.com/containerd/containerd
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
containerd image-triggered daemon crash via malformed digest in subject-annotated descriptor
CVE-2026-95839 / GHSA-vwhp-8p66-mq4f
More information
Details
Impact
A bug in containerd's image manifest processing causes an unrecovered panic when a child descriptor contains the
io.containerd.manifest.subjectannotation and a malformed digest. Pulling or importing such an image through the transfer service (including default CRIPullImagerequests) crashes the containerd daemon. In Kubernetes environments,kubeletretries failed image pulls with backoff, allowing a pod referencing an untrusted image to repeatedly crash containerd and disrupt container operations on the worker node.Patches
This bug has been fixed in containerd 2.4.2, 2.3.7, and 2.2.10. Users should update to these versions to resolve the issue.
Workarounds
Restrict pod image references to trusted registries (for example, using a Kubernetes
ValidatingAdmissionPolicyor admission webhook) and only pull or import images from trusted sources.Credits
The containerd project would like to thank @melihgurlek, LEI WANG (@ssst0n3) and Haoyuan Zhang (@zj1ng7), and OpenSec Intelligence who independently discovered and responsibly disclosed 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:4.0/AV:N/AC:L/AT:N/PR:L/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).
Release Notes
containerd/containerd (github.com/containerd/containerd/v2)
v2.3.7: containerd 2.3.7Compare Source
Welcome to the v2.3.7 release of containerd!
The seventh patch release for containerd 2.3 contains various fixes
and updates including security patches.
Security Updates
Highlights
Container Runtime Interface (CRI)
Image Distribution
Runtime
Snapshotters
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
31 commits
c8b271adbPrepare release notes for v2.3.7320278f96Update to go1.26.9ca3d94d2fMerge commit from fork9621a5f9cremotes/docker: bound parallel fetch readersdff0d82ddMerge commit from fork2181d7baaimages: skip malformed digests when computing referrer labels29ed4ba2eMerge commit from fork80885a94dcontent, remotes: bound reads to expected size5c6687786Merge commit from fork2e17e62e2cri: unmount checkpoint view on every CRImportCheckpoint return pathda23fb7afintegration/client: fix TestContainerExecLargeOutputWithTTY50a18659fcri: should not follow log file..path components that rewrite the host (#14281)b3dd30ae5reference: reject..path components that rewrite the host993898bbf[release/2.3] vendor: google.golang.org/grpc v1.83.2fe408f2a4core/unpack: tighten comments around id-mapping label filtering3ab5f9c0ecore/unpack: don't honor id-mapping labels from image annotations658428e2fseccomp: Use an allow-list for socket domainsc73186ea6Makefile: remove go mod download from integration030b7b3f7ci: skip linters steps in private repositoriesec6240e3eworkflows: skip non-CI jobs in private forks63092f411update runc binary to v1.5.2Dependency Changes
9d38bb4->3dc84a46f92a3b->3dc84a4Previous release can be found at v2.3.6
Which file should I download?
containerd-<VERSION>-<OS>-<ARCH>.tar.gz: ✅Recommended. Dynamically linked with glibc 2.35 (Ubuntu 22.04).containerd-static-<VERSION>-<OS>-<ARCH>.tar.gz: Statically linked. Expected to be used on Linux distributions that do not use glibc >= 2.35. 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.3.6: containerd 2.3.6Compare Source
Welcome to the v2.3.6 release of containerd!
The sixth patch release for containerd 2.3 contains various fixes
and updates including a security patch.
Security Updates
Highlights
Container Runtime Interface (CRI)
Image Storage
Runtime
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
26 commits
086fc0d40ePrepare release notes for v2.3.63e3b3daabcMerge commit from fork03fbef37daBound Walk referencesbfe167214bBound Dispatch concurrency and references5f17a29a9bcore/mount: Keep lazy copy for filtered options49796574fbcore/mount: Return copied filtered mount optionscb3f358aeamount: share lazy option filteringee7ae5b7c7mount: fix shallow copy of Options in RemoveVolatileOption and RemoveIDMapOption1facedfb21mount: fix input mutation in readonlyMounts5ca695a441mount: replace copyMounts with slices.Clone7fd198f858cri: tolerate wrapped ENOTSUP during relabel147edce99frelease: don't mark 2.3 releases as latestc2c5164437cri: only unmount image volumes when mounting fails74d0c79682cri: enable mount manager for image mounts4a3a41d353core/unpack: fetch layers of every config-sharing manifest9c6d7e9509pkg/oci: mask thermal interrupt infoac4464a399Update to go1.26.8f7f64ddc06Update to go1.26.7902a7d5e6cUpdate to go1.26.6Dependency Changes
This release has no dependency changes
Previous release can be found at v2.3.5
Which file should I download?
containerd-<VERSION>-<OS>-<ARCH>.tar.gz: ✅Recommended. Dynamically linked with glibc 2.35 (Ubuntu 22.04).containerd-static-<VERSION>-<OS>-<ARCH>.tar.gz: Statically linked. Expected to be used on Linux distributions that do not use glibc >= 2.35. 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.3.5: containerd 2.3.5Compare Source
Welcome to the v2.3.5 release of containerd!
The fifth patch release for containerd 2.3 contains various fixes
and updates including security patches.
Security Updates
Highlights
Image Distribution
Runtime
Snapshotters
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
33 commits
934efa5e0Prepare release notes for v2.3.5be419b070Merge commit from fork9ec55f024cri: cancel ExecSync IO drain on context cancellation84ea25bc1Merge commit from forkc53577965archive: skip redundant opaque whiteout walks9f6be869cFix data races and a deadlock in the byte stream helpers6c59399bfplugins: remove some stray logrus importsf65732115snapshots/erofs: test the advertised erofs feature platform5ffc2bbdaerofs: advertise the erofs OS feature platform from the snapshotteraf445ea0aupdate runc to v1.5.1c077e43bdupdate runc to v1.5.0676a64cadvendor: github.com/containerd/platforms v1.0.0-rc.5c7ffd8b00pkg/tracing: handle error and typed-nil Stringer attributes58fb846d5core/remotes/docker: normalize descriptor URL originsc7625a1ffcore/remotes/docker: strip sensitive headers on desc.urls fetch6fbb92c33update runhcs to v0.15.0-rc.453bf030eapkg/oci: resolve rootfs symlinks for user lookup7790c4c21ensure that the final config version is the higest in the config list1125b053fRevert "add check on version of drop in configs"460c47b28fix(runtime): bound shim loading with the load timeout7f97bc122Add more context to the shim delete errorChanges from containerd/platforms
2 commits
bacc690Fix WS2022 compat on hosts past the latest LTSCDependency Changes
Previous release can be found at v2.3.4
Which file should I download?
containerd-<VERSION>-<OS>-<ARCH>.tar.gz: ✅Recommended. Dynamically linked with glibc 2.35 (Ubuntu 22.04).containerd-static-<VERSION>-<OS>-<ARCH>.tar.gz: Statically linked. Expected to be used on Linux distributions that do not use glibc >= 2.35. 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: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.