OCPBUGS-95473: bump containerd to v1.7.33 for CVE-2026-53488

[Cragsmann]

Summary

• Bumps github.com/containerd/containerd from v1.7.32 to v1.7.33
• Fixes CVE-2026-53488: Host-root command execution via unvalidated image config labels in CRI plugin
• CVSS 8.3 (High)

Details

containerd CRI plugin propagates labels from image config (LABEL instruction in Dockerfile) to containers without validation. This can result in arbitrary command execution on the host via a crafted container image through the restart-monitor binary:// logger.

Patched in containerd 1.7.33.

Test plan

• go mod verify passes
• CI build succeeds
• No behavioral changes expected (indirect dependency bump)

Fixes: https://issues.redhat.com/browse/OCPBUGS-95473

[openshift-merge-bot]

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]

@Cragsmann: This pull request references Jira Issue OCPBUGS-95473, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

Details

In response to this:

Summary

• Bumps github.com/containerd/containerd from v1.7.32 to v1.7.33
• Fixes CVE-2026-53488: Host-root command execution via unvalidated image config labels in CRI plugin
• CVSS 8.3 (High)

Details

containerd CRI plugin propagates labels from image config (LABEL instruction in Dockerfile) to containers without validation. This can result in arbitrary command execution on the host via a crafted container image through the restart-monitor binary:// logger.

Patched in containerd 1.7.33.

Test plan

• go mod verify passes
• CI build succeeds
• No behavioral changes expected (indirect dependency bump)

Fixes: https://issues.redhat.com/browse/OCPBUGS-95473

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]

Warning

Review limit reached

@Cragsmann, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: d60c731f-320e-4a73-8306-745a853a29e3

📥 Commits

Reviewing files that changed from the base of the PR and between fd6a21a and d098820.

⛔ Files ignored due to path filters (5)

• go.sum is excluded by !**/*.sum
• vendor/github.com/containerd/containerd/labels/labels.go is excluded by !**/vendor/**, !vendor/**
• vendor/github.com/containerd/containerd/labels/validate.go is excluded by !**/vendor/**, !vendor/**
• vendor/github.com/containerd/containerd/version/version.go is excluded by !**/vendor/**, !vendor/**
• vendor/modules.txt is excluded by !**/vendor/**, !vendor/**

📒 Files selected for processing (1)

• go.mod

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Cragsmann
Once this PR has been reviewed and has the lgtm label, please assign rhamilto for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

@Cragsmann: 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.