OCPBUGS-79980,OCPBUGS-79981: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.67.3-sec.1 [release-4.16]

[rissh]

PR description

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

release-4.16 builds with Go 1.21 (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.67.3-sec.1 for Go 1.21.

Unlike release-4.17+, this branch had no existing grpc replace (baseline vendored grpc was v1.61.1). This PR adds:

replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go v1.67.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.17/4.18/4.19 workflow: product modules + vendor/ only (no tests-extension on this branch). No source changes; existing Conn.Connect() mitigation in OLM catalog grpc client remains unchanged.

Reference links

• Past 4.17 PR: OCPBUGS-80136,OCPBUGS-80137,OCPBUGS-80138: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.71.3-sec.1 [release-4.17] #1315
• 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.21): https://github.com/openshift-sustaining/grpc-go/releases/tag/v1.67.3-sec.1
• Upstream issue discussing grpc behavior: Unpin google.golang.org/grpc from go.mod operator-framework/operator-lifecycle-manager#3284

Test plan

• go list -m google.golang.org/grpc → v1.65.0 => github.com/openshift-sustaining/grpc-go v1.67.3-sec.1
• No v1.61.1 in vendor/modules.txt
• go test ./pkg/controller/registry/grpc/... (OLM)
• go mod verify
• go build -mod=vendor for cmd/olm and cmd/catalog
• OpenShift CI (e.g. e2e-gcp-olm)

[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: 922ba889-ae7d-4f36-9a5b-b9f6e5915f49

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

[openshift-ci-robot]

@rissh: This pull request references Jira Issue OCPBUGS-79980, 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-80136 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-79981, 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-80137 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:

PR description

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

release-4.16 builds with Go 1.21 (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.67.3-sec.1 for Go 1.21.

Unlike release-4.17+, this branch had no existing grpc replace (baseline vendored grpc was v1.61.1). This PR adds:

replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go v1.67.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.17/4.18/4.19 workflow: product modules + vendor/ only (no tests-extension on this branch). No source changes; existing Conn.Connect() mitigation in OLM catalog grpc client remains unchanged.

Reference links

• Past 4.17 PR: OCPBUGS-80136,OCPBUGS-80137,OCPBUGS-80138: Fix CVE-2026-33186 with openshift-sustaining/grpc-go v1.71.3-sec.1 [release-4.17] #1315
• 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.21): https://github.com/openshift-sustaining/grpc-go/releases/tag/v1.67.3-sec.1
• Upstream issue discussing grpc behavior: Unpin google.golang.org/grpc from go.mod operator-framework/operator-lifecycle-manager#3284

Test plan

• go list -m google.golang.org/grpc → v1.65.0 => github.com/openshift-sustaining/grpc-go v1.67.3-sec.1
• No v1.61.1 in vendor/modules.txt
• go test ./pkg/controller/registry/grpc/... (OLM)
• go mod verify
• go build -mod=vendor for cmd/olm and cmd/catalog
• 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rissh
Once this PR has been reviewed and has the lgtm label, please assign grokspawn 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:

• DOWNSTREAM_OWNERS

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

[rissh]

/hold
Dealing with ProdSec for trackers reported against the openshift4/ose-operator-registry-rhel9 component.

[openshift-ci]

@rissh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-console-olm	eb17c95	link	true	/test e2e-gcp-console-olm

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.