Skip to content

Update module github.com/containerd/containerd/v2 to v2.3.7 [SECURITY] (release-v0.9) - #3705

Open
red-hat-konflux[bot] wants to merge 1 commit into
release-v0.9from
konflux/mintmaker/release-v0.9-release-v0.9/go-github.com-containerd-containerd-v2-vulnerability
Open

red-hat-konflux[bot] wants to merge 1 commit into
release-v0.9from
konflux/mintmaker/release-v0.9-release-v0.9/go-github.com-containerd-containerd-v2-vulnerability

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/containerd/containerd/v2 v2.3.4 → v2.3.7 age confidence

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

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 Score: 4.6 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

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

To report a security issue in containerd:

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

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.subject annotation and a malformed digest. Pulling or importing such an image through the transfer service (including default CRI PullImage requests) crashes the containerd daemon. In Kubernetes environments, kubelet retries 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 ValidatingAdmissionPolicy or 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 Score: 7.1 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

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

Compare 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)
  • Apply hardening to not follow symlinks for container log files (#​14301)
Image Distribution
  • Apply hardening to reject image references with ".." path components (#​14281)
Runtime
  • Apply hardening to allowlist socket domains in the default seccomp profile (#​14248)
Snapshotters
  • Apply hardening to filter ID-mapping labels from image annotations during unpack (#​14261)

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

Contributors
  • Samuel Karp
  • Wei Fu
  • Maksym Pavlenko
  • Aysha Afrah Ziya
  • Derek McGowan
  • Sebastiaan van Stijn
  • Akihiro Suda
  • LEI WANG
  • Paweł Gronowski
  • Phil Estes
  • Vishal Srinivasan
  • syed abdul khaliq
  • 申玥
Changes
31 commits

  • Prepare release notes for v2.3.7 (#​14339)
  • Update to go1.26.9 (#​14353)
    • 320278f96 Update to go1.26.9
    • ca3d94d2f Merge commit from fork
    • 9621a5f9c remotes/docker: bound parallel fetch readers
    • dff0d82dd Merge commit from fork
    • 2181d7baa images: skip malformed digests when computing referrer labels
    • 29ed4ba2e Merge commit from fork
    • 80885a94d content, remotes: bound reads to expected size
    • 5c6687786 Merge commit from fork
    • 2e17e62e2 cri: unmount checkpoint view on every CRImportCheckpoint return path
  • integration/client: fix TestContainerExecLargeOutputWithTTY (#​14306)
    • da23fb7af integration/client: fix TestContainerExecLargeOutputWithTTY
  • cri: should not follow log file (#​14301)
  • reference: reject .. path components that rewrite the host (#​14281)
    • b3dd30ae5 reference: reject .. path components that rewrite the host
  • vendor: google.golang.org/grpc v1.83.2 (#​14263)
    • 993898bbf [release/2.3] vendor: google.golang.org/grpc v1.83.2
  • core/unpack: don't honor id-mapping labels from image annotations (#​14261)
    • fe408f2a4 core/unpack: tighten comments around id-mapping label filtering
    • 3ab5f9c0e core/unpack: don't honor id-mapping labels from image annotations
  • seccomp: Use an allow-list for socket domains (#​14248)
    • 658428e2f seccomp: Use an allow-list for socket domains
  • Conditional actions (#​14244)
    • c73186ea6 Makefile: remove go mod download from integration
    • 030b7b3f7 ci: skip linters steps in private repositories
    • ec6240e3e workflows: skip non-CI jobs in private forks
  • update runc binary to v1.5.2 (#​14240)

Dependency Changes
  • go.opentelemetry.io/otel v1.43.0 -> v1.44.0
  • go.opentelemetry.io/otel/metric v1.43.0 -> v1.44.0
  • go.opentelemetry.io/otel/sdk v1.43.0 -> v1.44.0
  • go.opentelemetry.io/otel/trace v1.43.0 -> v1.44.0
  • golang.org/x/crypto v0.53.0 -> v0.55.0
  • golang.org/x/mod v0.36.0 -> v0.38.0
  • golang.org/x/net v0.55.0 -> v0.58.0
  • golang.org/x/oauth2 v0.35.0 -> v0.36.0
  • golang.org/x/sync v0.21.0 -> v0.22.0
  • golang.org/x/sys v0.46.0 -> v0.47.0
  • golang.org/x/term v0.44.0 -> v0.45.0
  • golang.org/x/text v0.38.0 -> v0.41.0
  • google.golang.org/genproto/googleapis/api 9d38bb4 -> 3dc84a4
  • google.golang.org/genproto/googleapis/rpc 6f92a3b -> 3dc84a4
  • google.golang.org/grpc v1.80.0 -> v1.83.2

Previous 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.6

Compare 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)
  • Fix bug where container creation failed when SELinux relabeling was unsupported by the filesystem (#​14211)
  • Enable mount manager for image mounts in CRI (#​14147)
Image Storage
  • Ensure all layers are fetched when multiple manifests in an index share a config descriptor (#​14139)
Runtime
  • Avoid unexpected mutation of mount options in mount helpers (#​14192)
  • Mask /proc/interrupts and CPU thermal throttle sysfs paths in Linux containers by default (#​14144)

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

Contributors
  • Paweł Gronowski
  • Samuel Karp
  • Chris Henzie
  • Maksym Pavlenko
  • Wei Fu
  • Gao Xiang
  • Nan Liu
Changes
26 commits

  • 086fc0d40e Prepare release notes for v2.3.6
  • 3e3b3daabc Merge commit from fork
  • 03fbef37da Bound Walk references
  • bfe167214b Bound Dispatch concurrency and references
  • Fix input mutation in mount option helpers (#​14192)
    • 5f17a29a9b core/mount: Keep lazy copy for filtered options
    • 49796574fb core/mount: Return copied filtered mount options
    • cb3f358aea mount: share lazy option filtering
    • ee7ae5b7c7 mount: fix shallow copy of Options in RemoveVolatileOption and RemoveIDMapOption
    • 1facedfb21 mount: fix input mutation in readonlyMounts
    • 5ca695a441 mount: replace copyMounts with slices.Clone
  • cri: tolerate wrapped ENOTSUP during relabel (#​14211)
    • 7fd198f858 cri: tolerate wrapped ENOTSUP during relabel
  • release: don't mark 2.3 releases as latest (#​14180)
    • 147edce99f release: don't mark 2.3 releases as latest
  • cri: Backport image mount fixes 2.3 (#​14147)
    • c2c5164437 cri: only unmount image volumes when mounting fails
    • 74d0c79682 cri: enable mount manager for image mounts
  • core/unpack: fetch layers of every config-sharing manifest (#​14139)
    • 4a3a41d353 core/unpack: fetch layers of every config-sharing manifest
  • pkg/oci: mask thermal interrupt info (#​14144)
  • Update to go1.26.8 (#​14088)

Dependency 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.5

Compare 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
  • Apply hardening to strip sensitive authentication headers when fetching descriptor URLs (#​14030)
Runtime
  • Avoid hangs and data races when streaming container standard I/O in CRI (#​14094)
  • Fix missing error messages in OpenTelemetry trace attributes (#​14049)
  • Fix user and group lookup failures in container rootfs containing symlinked /etc/passwd or /etc/group (#​13999)
  • Fix configuration loading error when drop-in configuration files have a higher version than the root configuration (#​13995)
  • Avoid containerd startup hangs when loading shims (#​13983)
  • Add context to error when shim delete times out (#​13921)
  • Fix Windows Server 2022 container compatibility on host builds newer than the latest LTSC (containerd/platforms#34)
Snapshotters
  • Fix unpack failure for EROFS images containing the erofs OS feature (#​14062)

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

Contributors
  • Phil Estes
  • Samuel Karp
  • Derek McGowan
  • Sebastiaan van Stijn
  • Akhil Mohan
  • Maksym Pavlenko
  • Wei Fu
  • Oleh Konko
  • Austin Vazquez
  • Jing Chen
  • Martín Fernández
  • Paco Xu
  • XlabAI
  • Yuanliang Zhang
Changes
33 commits

  • 934efa5e0 Prepare release notes for v2.3.5
  • be419b070 Merge commit from fork
  • 9ec55f024 cri: cancel ExecSync IO drain on context cancellation
  • 84ea25bc1 Merge commit from fork
  • c53577965 archive: skip redundant opaque whiteout walks
  • Fix data races and a deadlock in the byte stream helpers (#​14094)
    • 9f6be869c Fix data races and a deadlock in the byte stream helpers
  • plugins: remove some stray logrus imports (#​14063)
    • 6c59399bf plugins: remove some stray logrus imports
  • snapshots/erofs: advertise the erofs OS feature from the snapshotter plugin (#​14062)
    • f65732115 snapshots/erofs: test the advertised erofs feature platform
    • 5ffc2bbda erofs: advertise the erofs OS feature platform from the snapshotter
  • update runc to v1.5.1 (#​14059)
  • vendor: github.com/containerd/platforms v1.0.0-rc.5 (#​14048)
    • 676a64cad vendor: github.com/containerd/platforms v1.0.0-rc.5
  • pkg/tracing: handle error and typed-nil Stringer attributes (#​14049)
    • c7ffd8b00 pkg/tracing: handle error and typed-nil Stringer attributes
  • docker fetcher: strip sensitive headers on descriptor URLs (#​14030)
    • 58fb846d5 core/remotes/docker: normalize descriptor URL origins
    • c7625a1ff core/remotes/docker: strip sensitive headers on desc.urls fetch
  • update runhcs to v0.15.0-rc.4 (#​13990)
  • pkg/oci: resolve rootfs symlinks for user lookup (#​13999)
    • 53bf030ea pkg/oci: resolve rootfs symlinks for user lookup
  • Revert "add check on version of drop in configs" (#​13995)
    • 7790c4c21 ensure that the final config version is the higest in the config list
    • 1125b053f Revert "add check on version of drop in configs"
  • fix(runtime): apply load timeout to load shim (#​13983)
    • 460c47b28 fix(runtime): bound shim loading with the load timeout
  • Add more context to the shim delete error (#​13921)
    • 7f97bc122 Add more context to the shim delete error

Changes from containerd/platforms
2 commits

Dependency Changes
  • github.com/containerd/platforms v1.0.0-rc.4 -> v1.0.0-rc.5

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)

  • 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

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.

@red-hat-konflux

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.26.7 -> 1.26.8

@coderabbitai

coderabbitai Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: 247fd6a0-35c3-4d0f-be3c-bd6107bf3a57

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

@fullsend-ai-review

fullsend-ai-review Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 5:45 AM UTC · Completed 5:54 AM UTC

Commit: e970982 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.56

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Nov 12, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

Risk Assessment: moderate (2/5)

Details

Bot-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 run

Risk Assessment: moderate (2/5)

Details

Bot-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)

Details

Small, 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.

@fullsend-ai-review

fullsend-ai-review Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

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)

Review

Reason: 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.

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added ready-for-merge All reviewers approved — ready to merge dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Nov 12, 2026
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/release-v0.9-release-v0.9/go-github.com-containerd-containerd-v2-vulnerability branch from e970982 to 8f8906f Compare November 12, 2026 14:52
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

🤖 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: 8f8906f · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.41

@fullsend-ai-review fullsend-ai-review Bot removed ready-for-merge All reviewers approved — ready to merge risk/moderate PR risk: moderate labels Nov 12, 2026
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/release-v0.9-release-v0.9/go-github.com-containerd-containerd-v2-vulnerability branch from 8f8906f to a0be785 Compare November 13, 2026 01:57
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 1:59 AM UTC · Completed 2:08 AM UTC

Commit: a0be785 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.93

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Nov 13, 2026
fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review November 13, 2026 02:08

Superseded by updated review

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Nov 13, 2026
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/release-v0.9-release-v0.9/go-github.com-containerd-containerd-v2-vulnerability branch from a0be785 to faf7fdb Compare November 21, 2026 04:00
@red-hat-konflux red-hat-konflux Bot changed the title Update module github.com/containerd/containerd/v2 to v2.3.6 [SECURITY] (release-v0.9) Update module github.com/containerd/containerd/v2 to v2.3.7 [SECURITY] (release-v0.9) Nov 21, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 21, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 4:02 AM UTC · Completed 4:14 AM UTC

Commit: faf7fdb · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.10

@fullsend-ai-review fullsend-ai-review Bot removed the ready-for-merge All reviewers approved — ready to merge label Nov 21, 2026
@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review November 21, 2026 04:14

Superseded by updated review

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Nov 21, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update Go code ready-for-merge All reviewers approved — ready to merge renovate risk/moderate PR risk: moderate security size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants