Skip to content

NO-JIRA: Bump containerd to v1.7.33 to fix CVE - #144

Open
matejvasek wants to merge 1 commit into
openshift:mainfrom
matejvasek:no-jira-bump-containerd-for-cve-fix
Open

NO-JIRA: Bump containerd to v1.7.33 to fix CVE#144
matejvasek wants to merge 1 commit into
openshift:mainfrom
matejvasek:no-jira-bump-containerd-for-cve-fix

Conversation

@matejvasek

Copy link
Copy Markdown

Summary

Addresses CVE-2026-53488 (CRI label injection / host-root exec in containerd). Bumps github.com/containerd/containerd from v1.7.24 to v1.7.33.

Additional Info

As for the RIT process documentation the Jira ticket is not attached to this PR, I quote:

In some cases, a symbol level analysis will show that the component is not actually exposed to the vulnerability. In these cases the package should still be updated, but not attached to the bug.

Call-graph reachability analysis (VTA, 429K edges) confirmed that the vulnerable CRI plugin code (pkg/cri/) is not vendored and not reachable from production code. The only reachable containerd code is containerd/archive.Apply, used for OCI image layer unpacking.

References

Bump github.com/containerd/containerd to v1.7.33 to address
CVE-2026-53488 (CRI label injection / host-root exec). Symbol-level
analysis confirms the vulnerable CRI plugin code is not vendored
or reachable from production code.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@matejvasek: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

Addresses CVE-2026-53488 (CRI label injection / host-root exec in containerd). Bumps github.com/containerd/containerd from v1.7.24 to v1.7.33.

Additional Info

As for the RIT process documentation the Jira ticket is not attached to this PR, I quote:

In some cases, a symbol level analysis will show that the component is not actually exposed to the vulnerability. In these cases the package should still be updated, but not attached to the bug.

Call-graph reachability analysis (VTA, 429K edges) confirmed that the vulnerable CRI plugin code (pkg/cri/) is not vendored and not reachable from production code. The only reachable containerd code is containerd/archive.Apply, used for OCI image layer unpacking.

References

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.

@openshift-ci
openshift-ci Bot requested review from joelanford and oceanc80 July 10, 2026 14:53
@tmshort

tmshort commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

There's no bug associated with is?
I'm also a bit concerned that there's no CI running?
/approve

@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: matejvasek, 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 Jul 27, 2026
@tmshort

tmshort commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Before this is LGTM'd and verified, has it been built?

@matejvasek

Copy link
Copy Markdown
Author

There's no bug associated with is?
I'm also a bit concerned that there's no CI running?

The bug associated with this is OCPBUGS-95463, but we do not actually call the vulnerable functions. IIUC in such a case no bug should be associated in PR, since the bump is not necessary -- we don not really fix anything, but we still want to bump the dependency to avoid automatically reported vulnerabilities.

The absence of CI is really not confidence inspiring.

I tried make build locally and it worked.

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/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants