Repository navigation
Update module github.com/containerd/containerd/v2 to v2.3.6 [SECURITY] (main) - #3605
renovate[bot] wants to merge 1 commit into
Conversation
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly identifies the containerd module update to v2.3.6 and marks it as a security change. The trailing branch name is unnecessary but does not obscure the main change. |
| Description check | |
The description explains what changed and why, including the addressed security advisories and release details. It does not use the required What, Why, and Tickets headings, and it provides no ticket … |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Description check
-
Explanation
The description explains what changed and why, including the addressed security advisories and release details. It does not use the required What, Why, and Tickets headings, and it provides no ticket link, but the missing ticket information is non-critical.
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches: 💡 1
-
🛠️ Fix failing CI checks: 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
Comment @coderabbitai help to get the list of available commands.
|
<!-- fullsend:risk-assessment --> DetailsRenovate bot security bump of containerd/v2 touching only go.mod and go.sum; Tier 1 signals are identical to the prior assessment with DEPENDENCY_FILES_CHANGED=2 as the sole elevated factor, offset by bot authorship, zero protected paths, and an 8-line diff; Tier 2 shows zero 30-day churn with mild elevation from four distinct authors in 90 days and a single revert in history; the 62/38 weighted composite is 0.62x1.50 + 0.38x1.86 = 1.64, which rounds to 2, anchoring to the prior score. Previous run<!-- fullsend:risk-assessment --> DetailsRenovate bot security bump of containerd/v2 touching only go.mod and go.sum; Tier 1 signals are identical to the prior assessment with DEPENDENCY_FILES_CHANGED=2 as the only elevated factor, offset by bot authorship, zero protected paths, and tiny diff; Tier 2 shows zero 30-day churn but mild elevation from workaround-pattern commit history, keeping the 62/38 weighted composite at ~1.85, which rounds to 2. Previous run (2)Risk Assessment: moderate (2/5) DetailsRenovate bot security bump of containerd/v2 (v2.3.4->v2.3.6 patching 3 CVEs) touching only go.mod and go.sum. Tier 1 signals are identical to the prior assessment — DEPENDENCY_FILES_CHANGED=2 is the only elevated factor, offset by bot authorship, zero protected paths, tiny diff, and no security-sensitive path changes. Tier 2 is clean: zero 30-day churn, no reverts, routine dependency-update history. Weighted composite (62/38, no linked issue) ~=1.62 rounds to 2. Re-review anchoring confirms no new signal warrants a score change from the prior moderate assessment. Previous run (3)Risk Assessment: moderate (2/5) DetailsRenovate bot security bump of containerd/v2 (v2.3.4->v2.3.6 patching CVE-2026-53495 and CVE-2026-53493) touching only go.mod and go.sum; elevated by structural monorepo change-coupling and the >=2 dependency files signal, but the tiny diff, bot authorship, and clean 90-day history keep the composite at moderate. Previous run (4)Risk Assessment: moderate (2/5) DetailsXS security bump by trusted renovate bot updating containerd/v2 from v2.3.4 to v2.3.6 (two CVEs patched) plus go directive patch in dependency manifests only; dependency file changes remain the sole elevated signal, offset by bot authorship, zero protected paths, no CI changes, and stable low-churn git history. Previous run (5)Risk Assessment: moderate (2/5) DetailsTiny XS security bump by trusted bot touching only dependency manifests (go.mod/go.sum); dependency file changes are the sole elevated signal, offset by well-managed update history and an indirect-only containerd CVE fix. Previous run (6)Risk Assessment: moderate (2/5) DetailsAutomated renovate-bot dependency bump of go.mod and go.sum (2 files, 8 lines, small blast radius) with no recent churn and low fix/revert history; the sole risk driver remains ≥2 dependency files changed, yielding a Tier 1 average of 1.5 and Tier 2 average of 1.25 for a composite of ~1.4, anchored to the prior verified score of 2 (moderate). Previous run (7)Risk Assessment: moderate (2/5) DetailsAutomated renovate-bot security bump of only go.mod and go.sum (2 files, 8 lines, small blast radius) patching two containerd CVEs; the sole risk driver is having ≥2 dependency files changed, while all other signals (churn, blast radius, CI, protected paths) are minimal, yielding a composite of 1.53 rounded to 2. Previous run (8)Risk Assessment: moderate (2/5) DetailsAutomated security update for containerd/v2 with a minimal 2-file, 8-line diff; risk is limited to the presence of two dependency files changed (go.mod + go.sum), which is standard for any Go dependency bump, while all other signals (blast radius, author, protected paths, churn) are low. Previous run (9)Risk Assessment: moderate (2/5) DetailsRenovate bot PR modifying only go.mod and go.sum (2 files, 8 lines, small blast radius) to patch two containerd CVEs; the ≥2 dependency files changed raises Tier 1 to 1.5, and moderate author diversity plus moderate file staleness (~33 days) bring Tier 2 to ~1.86, producing a weighted composite of 0.62×1.5 + 0.38×1.86 ≈ 1.64, rounded to 2 (moderate). |
|
Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous runLooks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (2)Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (3)Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (4)Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (5)Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (6)Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (7)Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (8)Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (9)Looks good to me <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
added
the
ready-for-merge
60bef75 to
f014061
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Superseded by updated review
f014061 to
f5e024a
Compare
Superseded by updated review
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
f5e024a to
c89c631
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Superseded by updated review
c89c631 to
a7d7fce
Compare
Superseded by updated review
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
a7d7fce to
269c140
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Superseded by updated review
269c140 to
1e5f23b
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Superseded by updated review
1e5f23b to
f91d77d
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Superseded by updated review
f91d77d to
5ca8869
Compare
Superseded by updated review
fullsend-ai-review
Bot
added
requires-manual-review
5ca8869 to
4033a4f
Compare
fullsend-ai-review
Bot
added
ready-for-merge
This PR contains the following updates:
v2.3.4→v2.3.6containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service
CVE-2026-53495 / GHSA-7jxh-36q5-gcqv
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 the GitHub Advisory Database (CC-BY 4.0).
Containerd has image-pull DoS via crafted OCI index graph amplification
CVE-2026-53493 / GHSA-pg57-6jwg-q645
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 the GitHub Advisory Database (CC-BY 4.0).
containerd: Unpack DoS via repeated opaque whiteouts
CVE-2026-95838 / GHSA-rp3h-jf77-q9p4
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 the GitHub Advisory Database (CC-BY 4.0).
Release Notes
containerd/containerd (github.com/containerd/containerd/v2)
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.
This PR was generated by Mend Renovate. View the repository job log.