[release-4.18] OCPBUGS-80219: Fix CVE-2026-33186 using openshift-sustaining grpc-go fork

[katekeiroz-dev]

Summary

Fix CVE-2026-33186 (gRPC-Go authorization bypass due to improper HTTP/2 path validation) on release-4.18.

Uses the openshift-sustaining/grpc-go v1.71.3-sec.1 fork via a replace directive in go.mod. This fork patches the CVE while remaining compatible with Go 1.22 (the release-4.18 CI toolchain).

Changes

• Added replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go v1.71.3-sec.1 to go.mod
• Transitive dependency bumps from MVS (minimal, Go 1.22-compatible)

Why the fork?

Upstream grpc-go v1.79.3 (which fixes the CVE directly) transitively requires Go 1.24+ dependencies (go-jose/go-jose/v4@v4.1.3, cloud.google.com/go/compute/metadata), which are incompatible with the release-4.18 CI builder image (Go 1.22.9/1.22.12).

Related: OCPBUGS-80219

[openshift-ci-robot]

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-80219, which is invalid:

• expected dependent Jira Issue OCPBUGS-80400 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST 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:

Update google.golang.org/grpc to v1.79.3 to address CVE-2026-33186 (gRPC-Go authorization bypass due to improper HTTP/2 path validation).

Related: OCPBUGS-80219

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: 7b1131be-54fe-4ab6-bdb7-8bdc5ad74346

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[katekeiroz-dev]

/ok-to-test

[katekeiroz-dev]

/retest-required

[katekeiroz-dev]

/retest-required

[katekeiroz-dev]

/retest-required

[dlom]

/jira refresh

[openshift-ci-robot]

@dlom: This pull request references Jira Issue OCPBUGS-80219, 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.18.z) matches configured target version for branch (4.18.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-80400 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-80400 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.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.

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

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.

[dlom]

/retest

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.70%. Comparing base (363e98b) to head (3dc4cfe).

Additional details and impacted files

@@              Coverage Diff              @@
##           release-4.18    #1041   +/-   ##
=============================================
  Coverage         46.70%   46.70%           
=============================================
  Files                97       97           
  Lines             11970    11970           
=============================================
  Hits               5590     5590           
  Misses             5763     5763           
  Partials            617      617           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[openshift-ci]

@katekeiroz-dev: 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/security	3dc4cfe	link	true	/test security

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.