Skip to content

[release-4.21] OCPBUGS-95444 OCPBUGS-95447: bumping containerd to v1.7.33 - #1354

Open
AkashMore08 wants to merge 1 commit into
openshift:release-4.21from
AkashMore08:release-4.21_CVE-2026-53488
Open

[release-4.21] OCPBUGS-95444 OCPBUGS-95447: bumping containerd to v1.7.33#1354
AkashMore08 wants to merge 1 commit into
openshift:release-4.21from
AkashMore08:release-4.21_CVE-2026-53488

Conversation

@AkashMore08

@AkashMore08 AkashMore08 commented Aug 18, 2026

Copy link
Copy Markdown

OCPBUGS-95444: Bump github.com/containerd/containerd to v1.7.33 to remediated the CVE-2026-53488

Summary

  • Bump github.com/containerd/containerd from v1.7.29 to v1.7.33 to address CVE-2026-53488
  • CVE-2026-53488: Host-root command execution via unvalidated image config labels in containerd CRI plugin
  • This component uses containerd only as a library for OCI image operations and is NOT affected by the CVE (CRI plugin code is not vendored), but bumping to the fixed version as a best practise.

Transitive dependency bumps

  • github.com/moby/spdystream v0.5.0 → v0.5.1

Test plan

  • go build ./cmd/... passes
  • go test ./... passes (pre-existing grpc-health-probe import error unrelated)
  • go list -deps ./cmd/... confirms containerd is not compiled into any production binary

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@AkashMore08: This pull request references Jira Issue OCPBUGS-95444, which is invalid:

  • expected dependent Jira Issue OCPBUGS-95458 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

OCPBUGS-95444: Bump github.com/containerd/containerd to v1.7.33 to remediated the CVE-2026-53488

Summary
Bump github.com/containerd/containerd from v1.7.29 to v1.7.33 to address CVE-2026-53488
CVE-2026-53488: Host-root command execution via unvalidated image config labels in containerd CRI plugin
This component uses containerd only as a library for OCI image operations and is NOT affected by the CVE (CRI plugin code is not vendored), but bumping to the fixed version as a best practise.

Transitive dependency bumps
github.com/cyphar/filepath-securejoin v0.4.1 → v0.5.1
github.com/moby/spdystream v0.5.0 → v0.5.1
github.com/opencontainers/selinux v1.12.0 → v1.13.1

Test plan
go build ./cmd/... passes
go test ./... passes (pre-existing grpc-health-probe import error unrelated)
go list -deps ./cmd/... confirms containerd is not compiled into any production binary

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented Aug 18, 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

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e764efa6-0200-4b69-a2ff-fff5cf1c551a

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci
openshift-ci Bot requested review from dtfranz and tmshort August 18, 2026 09:33
@AkashMore08 AkashMore08 changed the title [release-4.21] OCPBUGS-95444: bumping containerd to v1.7.33 [release-4.21] OCPBUGS-95444 OCPBUGS-95447: bumping containerd to v1.7.33 Aug 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@AkashMore08: This pull request references Jira Issue OCPBUGS-95444, which is invalid:

  • expected dependent Jira Issue OCPBUGS-95458 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-95447, which is invalid:

  • expected dependent Jira Issue OCPBUGS-95441 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

OCPBUGS-95444: Bump github.com/containerd/containerd to v1.7.33 to remediated the CVE-2026-53488

Summary

  • Bump github.com/containerd/containerd from v1.7.29 to v1.7.33 to address CVE-2026-53488
  • CVE-2026-53488: Host-root command execution via unvalidated image config labels in containerd CRI plugin
  • This component uses containerd only as a library for OCI image operations and is NOT affected by the CVE (CRI plugin code is not vendored), but bumping to the fixed version as a best practise.

Transitive dependency bumps

  • github.com/moby/spdystream v0.5.0 → v0.5.1

Test plan

  • go build ./cmd/... passes
  • go test ./... passes (pre-existing grpc-health-probe import error unrelated)
  • go list -deps ./cmd/... confirms containerd is not compiled into any production binary

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@tmshort

tmshort commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-olmv0-ext

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console-olm
/test e2e-gcp-olm
/test e2e-gcp-ovn
/test e2e-upgrade

@openshift-ci

openshift-ci Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AkashMore08, tmshort

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 19, 2026
@tmshort

tmshort commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

/retest

@openshift-ci

openshift-ci Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

@AkashMore08: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants