[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/containerd/containerd	v1.7.33 → v1.7.36

---

containerd: 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:

• Open an issue in containerd
• Send an email to security@containerd.io

To report a security issue in containerd:

• Report a new vulnerability
• Send an email to security@containerd.io

Severity

• CVSS Score: 6.8 / 10 (Medium)
• Vector String: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

• https://github.com/containerd/containerd/security/advisories/GHSA-7jxh-36q5-gcqv
• https://github.com/containerd/containerd/releases/tag/v1.7.35
• https://github.com/containerd/containerd/releases/tag/v2.0.12
• https://github.com/containerd/containerd/releases/tag/v2.2.8
• https://github.com/containerd/containerd/releases/tag/v2.3.5
• https://github.com/advisories/GHSA-7jxh-36q5-gcqv

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 PullImage operation, 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:

• Open an issue in containerd
• Email us at security@containerd.io

To report a security issue in containerd:

• Report a new vulnerability
• Email us at security@containerd.io

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/containerd/containerd/security/advisories/GHSA-pg57-6jwg-q645
• https://nvd.nist.gov/vuln/detail/CVE-2026-53493
• https://github.com/containerd/containerd/commit/4f5f32636d47f051751065cf824a10da70c619fe
• https://github.com/containerd/containerd/commit/94e83c14c8aac963e24e28105dab9c9af812a2a8
• https://github.com/containerd/containerd/releases/tag/v1.7.36
• https://github.com/containerd/containerd/releases/tag/v2.0.13
• https://github.com/containerd/containerd/releases/tag/v2.2.9
• https://github.com/containerd/containerd/releases/tag/v2.3.6
• https://github.com/containerd/containerd/releases/tag/v2.4.1
• https://github.com/advisories/GHSA-pg57-6jwg-q645

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

containerd/containerd (github.com/containerd/containerd)

v1.7.36: containerd 1.7.36

Compare Source

Welcome to the v1.7.36 release of containerd!

The thirty-sixth patch release for containerd 1.7 contains various fixes
and updates including a security patch.

Security Updates

• containerd
  • CVE-2026-53493

Highlights

Image Storage

• Ensure all layers are fetched when multiple manifests in an index share a config descriptor (#​14142)

Runtime

• Mask /proc/interrupts and CPU thermal throttle sysfs paths in Linux containers by default (#​14184)

Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.

Contributors

• Samuel Karp
• Chris Henzie
• Derek McGowan

Changes

9 commits

• b0ab39c205 Prepare release notes for v1.7.36
• 670a5de22f Merge commit from fork
• a3a39e5873 Bound Walk references
• ffc673f859 Bound Dispatch concurrency and references
• pkg/oci: mask thermal interrupt info (#​14184)
  • 19334a4d7e pkg/oci: mask thermal interrupt info
• core/unpack: fetch layers of every config-sharing manifest (#​14142)
  • 4684c683c2 core/unpack: fetch layers of every config-sharing manifest
  • 7fba9f7c3c Create new imagetest package

Dependency Changes

This release has no dependency changes

Previous release can be found at v1.7.35

v1.7.35: containerd 1.7.35

Compare Source

Welcome to the v1.7.35 release of containerd!

The thirty-fifth patch release for containerd 1.7 contains various fixes
and updates including security patches.

Security Updates

• containerd
  • CVE-2026-53495
  • GHSA-rp3h-jf77-q9p4

Highlights

Image Distribution

• Apply hardening to strip sensitive authentication headers when fetching descriptor URLs (#​14046)

Runtime

• Enable log scrubbing by default on Windows (#​13889)

Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.

Contributors

• Samuel Karp
• Oleh Konko
• Chris Henzie
• Maksym Pavlenko
• Phil Estes
• XlabAI

Changes

13 commits

• 05aa78da3 Prepare release notes for v1.7.35
• 3bd79bb36 Merge commit from fork
• 5a2a3a759 cri: cancel ExecSync IO drain on context cancellation
• 323e148f2 Merge commit from fork
• 9205b1903 archive: skip redundant opaque whiteout walks
• docker fetcher: strip sensitive headers on descriptor URLs (#​14046)
  • b01d66349 core/remotes/docker: normalize descriptor URL origins
  • b5d936dca core/remotes/docker: strip sensitive headers on desc.urls fetch
• Use ScrubLogs by default on Windows (#​13889)
  • cff94ea40 ctr: add --scrub-logs flag for Windows
  • 544e4657d cri/config: use ScrubLogs by default on Windows
• ci: bound Go fuzzing by execution count (#​13788)
  • 71e00ba9c ci: bound Go fuzzing by execution count

Dependency Changes

This release has no dependency changes

Previous release can be found at v1.7.34

v1.7.34: containerd 1.7.34

Compare Source

Welcome to the v1.7.34 release of containerd!

The thirty-fourth patch release for containerd 1.7 contains various fixes and updates.

Highlights

Container Runtime Interface (CRI)

• Fix lost container exit events when events arrive before container info is cached (#​11634)

Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.

Contributors

• Chris Henzie
• Samuel Karp
• Akihiro Suda
• Maksym Pavlenko
• Phil Estes
• Sopho Merkviladze
• ningmingxiao

Changes

5 commits

• Prepare release notes for v1.7.34 (#​13753)
  • 7db112471 Prepare release notes for v1.7.34
• Update go to 1.26.5/1.25.12 (#​13731)
  • c06144c85 Update go to 1.26.5/1.25.12
• ci: pin fog-json to resolve gem conflict (#​13712)
  • b84460e50 ci: pin fog-json to resolve gem conflict
• cri:fix lost container exit events if they arrive before info is cached (#​11634)
  • 2fe076ea7 cri:fix lost container exit events if they arrive before info is cached
• build(deps): bump golang.org/x/* dependencies (#​13502)
  • 862057716 bump golang.org/x/* dependencies

Dependency Changes

• golang.org/x/crypto v0.45.0 -> v0.52.0
• golang.org/x/mod v0.29.0 -> v0.35.0
• golang.org/x/net v0.47.0 -> v0.55.0
• golang.org/x/sync v0.18.0 -> v0.20.0
• golang.org/x/sys v0.38.0 -> v0.45.0
• golang.org/x/term v0.37.0 -> v0.43.0
• golang.org/x/text v0.31.0 -> v0.37.0

Previous release can be found at v1.7.33

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7f8d5212-731d-4874-b0ac-337e2a4d6722

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
acceptance	54.86% <ø> (ø)
generative	18.14% <ø> (ø)
integration	26.99% <ø> (ø)
unit	68.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 11:23 PM UTC · Completed 11:27 PM UTC

Commit: 4918659 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $2.20

[fullsend-ai-retro]

Retro: PR #3612 — nothing to retrospect on

PR #3612 was authored by Renovate, targeted release-v0.8, and was auto-closed by Renovate ~28 hours later without being merged. The container-related sibling PR #3613 (upgrade to containerd/v2 v2.3.6) remains open and supersedes it — a textbook Renovate autoclose.

Zero agent activity occurred on this PR. Dispatch run 38653608775 shows every stage (code, review, fix, triage, prioritize) skipped — only Retro ran. No human review was submitted. The reviews, timeline, and retro agent therefore have no agent behaviour, no human/agent delta, and no rework-rate signal to analyze.

No proposals filed — this exact pattern is already extensively tracked. Filing anything here would duplicate open work:

• fullsend-ai/fullsend#4006 — "Skip retro stage for automated dependency PRs (Renovate, Dependabot, MintMaker)" — names Renovate explicitly, directly covers this case.
• fullsend-ai/fullsend#3833, #7392, #7486, #7197, #7452, #7803 — overlapping variants of "skip retro on bot-authored / zero-agent-activity PRs".
• fullsend-ai/fullsend#2471, #2524 — adjacent (unmerged PRs, premature runs).
• fullsend-ai/fullsend#8029 — fix the misleading ADR 0054 citation in the closed) STAGE="retro" comment in reusable-dispatch.yml.
• fullsend-ai/agents#276, #349, #198 — pre-retro.sh early-exit variants; agent-layer counterpart to the above.
• conforma/.fullsend#3985 — org-level tracker of serial Renovate autoclose churn in this repo.

Evidence this retro adds for fullsend-ai/fullsend#4006 and fullsend-ai/agents#349: in conforma/cli over the last 60 days, 7/7 Renovate autoclosed PRs (#3616, #3612, #3608, #3507, #3456, #3462, #3338) each triggered a retro dispatch within 3–5 seconds of close with every non-retro stage skipped. 100% zero-value firing rate in this repo's recent sample.

Root cause (for the implementers of the issues above): reusable-dispatch.yml at fullsend-ai/fullsend@ea66a0a lines 351–368 unconditionally sets STAGE="retro" on pull_request_target.closed, with no gate on merged-vs-closed, author type, or prior-stage activity. The job gate at line 1313 (if: needs.route.outputs.stage == 'retro') then fires regardless.