OCPBUGS-80136,OCPBUGS-80137,OCPBUGS-80138: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.71.3-sec.1 [release-4.17]

[rissh]

PR description

This change addresses CVE-2026-33186 / GHSA-p77j-4mvh-x3m3 / GO-2026-4762 in product Go modules for release-4.17 and refreshes the root vendor/ tree accordingly.

release-4.17 builds with Go 1.22 (see .ci-operator.yaml). Upstream google.golang.org/grpc v1.79.3 requires Go 1.24, so this PR uses the OpenShift sustaining backport v1.71.3-sec.1 for Go 1.22.

For this branch, we removed the legacy grpc downgrade replace (google.golang.org/grpc => v1.63.2) and replaced it with:

replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go v1.71.3-sec.1

in the root go.mod and staging/operator-lifecycle-manager/go.mod, so the effective vendored grpc is patched.

Scope matches release-4.18/4.19 workflow: product modules + vendor/ only (no tests-extension on this branch). Existing prometheus #3283 replaces are unchanged.

Reference links

• Past 4.18 PR: OCPBUGS-80311,OCPBUGS-80312,OCPBUGS-80313: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.71.3-sec.1 [release-4.18] #1314
• Past 4.19 PR: OCPBUGS-80492,OCPBUGS-80493,OCPBUGS-80494: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.75.1-sec.1 [release-4.19] #1310
• OpenShift sustaining grpc backport (Go 1.22): https://github.com/openshift-sustaining/grpc-go/releases/tag/v1.71.3-sec.1
• Upstream issue discussing grpc unpin: Unpin google.golang.org/grpc from go.mod operator-framework/operator-lifecycle-manager#3284

Test plan

• go list -m google.golang.org/grpc → v1.70.0 => github.com/openshift-sustaining/grpc-go v1.71.3-sec.1
• No v1.63.2 in vendor/modules.txt
• go test ./pkg/controller/registry/grpc/... (OLM)
• go mod verify
• OpenShift CI (e.g. e2e-gcp-olm)

[openshift-ci-robot]

@rissh: This pull request references Jira Issue OCPBUGS-80136, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-80311 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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-80137, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-80312 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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-80138, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-80313 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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:

PR description

This change addresses CVE-2026-33186 / GHSA-p77j-4mvh-x3m3 / GO-2026-4762 in product Go modules for release-4.17 and refreshes the root vendor/ tree accordingly.

release-4.17 builds with Go 1.22 (see .ci-operator.yaml). Upstream google.golang.org/grpc v1.79.3 requires Go 1.24, so this PR uses the OpenShift sustaining backport v1.71.3-sec.1 for Go 1.22.

For this branch, we removed the legacy grpc downgrade replace (google.golang.org/grpc => v1.63.2) and replaced it with:

replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go v1.71.3-sec.1

in the root go.mod and staging/operator-lifecycle-manager/go.mod, so the effective vendored grpc is patched.

Scope matches release-4.18/4.19 workflow: product modules + vendor/ only (no tests-extension on this branch). Existing prometheus #3283 replaces are unchanged.

Reference links

• Past 4.18 PR: OCPBUGS-80311,OCPBUGS-80312,OCPBUGS-80313: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.71.3-sec.1 [release-4.18] #1314
• Past 4.19 PR: OCPBUGS-80492,OCPBUGS-80493,OCPBUGS-80494: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.75.1-sec.1 [release-4.19] #1310
• OpenShift sustaining grpc backport (Go 1.22): https://github.com/openshift-sustaining/grpc-go/releases/tag/v1.71.3-sec.1
• Upstream issue discussing grpc unpin: Unpin google.golang.org/grpc from go.mod operator-framework/operator-lifecycle-manager#3284

Test plan

• go list -m google.golang.org/grpc → v1.70.0 => github.com/openshift-sustaining/grpc-go v1.71.3-sec.1
• No v1.63.2 in vendor/modules.txt
• go test ./pkg/controller/registry/grpc/... (OLM)
• go mod verify
• OpenShift CI (e.g. e2e-gcp-olm)

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]

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

Run ID: 3ef04386-308a-467c-8e41-f1e61809062a

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

✨ 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 and usage tips.}

[rissh]

/retest

[MrSanketkumar]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.z) matches configured target version for branch (4.17.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-80311 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-80311 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.z) matches configured target version for branch (4.17.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-80312 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-80312 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.z) matches configured target version for branch (4.17.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-80313 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-80313 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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]

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

[MrSanketkumar]

/tide refresh

[MrSanketkumar]

/tide

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, rissh

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:

• DOWNSTREAM_OWNERS [grokspawn]

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

[MrSanketkumar]

/verified By CI

All go.mod files are using the same gRPC patch version provided by the Sustaining Team and verified that it is compatible with the Go version.

[openshift-ci-robot]

@MrSanketkumar: This PR has been marked as verified by CI.

Details

In response to this:

/verified By CI

All go.mod files are using the same gRPC patch version provided by the Sustaining Team and verified that it is compatible with the Go version.

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.

[prabhapa]

/label backport-risk-assessed

[openshift-ci-robot]

@rissh: Jira Issue Verification Checks: Jira Issue OCPBUGS-80136
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-80136 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Jira Issue Verification Checks: Jira Issue OCPBUGS-80137
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-80137 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Jira Issue Verification Checks: Jira Issue OCPBUGS-80138
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-80138 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

PR description

This change addresses CVE-2026-33186 / GHSA-p77j-4mvh-x3m3 / GO-2026-4762 in product Go modules for release-4.17 and refreshes the root vendor/ tree accordingly.

release-4.17 builds with Go 1.22 (see .ci-operator.yaml). Upstream google.golang.org/grpc v1.79.3 requires Go 1.24, so this PR uses the OpenShift sustaining backport v1.71.3-sec.1 for Go 1.22.

For this branch, we removed the legacy grpc downgrade replace (google.golang.org/grpc => v1.63.2) and replaced it with:

replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go v1.71.3-sec.1

in the root go.mod and staging/operator-lifecycle-manager/go.mod, so the effective vendored grpc is patched.

Scope matches release-4.18/4.19 workflow: product modules + vendor/ only (no tests-extension on this branch). Existing prometheus #3283 replaces are unchanged.

Reference links

• Past 4.18 PR: OCPBUGS-80311,OCPBUGS-80312,OCPBUGS-80313: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.71.3-sec.1 [release-4.18] #1314
• Past 4.19 PR: OCPBUGS-80492,OCPBUGS-80493,OCPBUGS-80494: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.75.1-sec.1 [release-4.19] #1310
• OpenShift sustaining grpc backport (Go 1.22): https://github.com/openshift-sustaining/grpc-go/releases/tag/v1.71.3-sec.1
• Upstream issue discussing grpc unpin: Unpin google.golang.org/grpc from go.mod operator-framework/operator-lifecycle-manager#3284

Test plan

• go list -m google.golang.org/grpc → v1.70.0 => github.com/openshift-sustaining/grpc-go v1.71.3-sec.1
• No v1.63.2 in vendor/modules.txt
• go test ./pkg/controller/registry/grpc/... (OLM)
• go mod verify
• OpenShift CI (e.g. e2e-gcp-olm)

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.