Skip to content

[release-4.21] OCPBUGS-80749: Bump google.golang.org/grpc to v1.79.3#293

Open
rh-soboh wants to merge 1 commit intoopenshift:release-4.21from
rh-soboh:release-4.21
Open

[release-4.21] OCPBUGS-80749: Bump google.golang.org/grpc to v1.79.3#293
rh-soboh wants to merge 1 commit intoopenshift:release-4.21from
rh-soboh:release-4.21

Conversation

@rh-soboh
Copy link
Copy Markdown

@rh-soboh rh-soboh commented May 7, 2026

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

Bump google.golang.org/grpc from v1.71.3 to v1.79.3 to address
CVE-2026-33186 (gRPC-Go authorization bypass).

Commands used:
  go get google.golang.org/grpc@v1.79.3
  go mod tidy
  go mod vendor
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 7, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@rh-soboh: This pull request references Jira Issue OCPBUGS-80749, 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.

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:

Summary

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

Changes

  • Updated google.golang.org/grpc from v1.71.3 to v1.79.3
  • Updated transitive dependencies (golang.org/x/net, golang.org/x/crypto, otel, protobuf, etc.)
  • Ran go mod tidy and go mod vendor

CVE Details

CVE-2026-33186: gRPC-Go authorization bypass due to improper HTTP/2 path validation

  • Severity: High
  • Affected: gRPC-Go < 1.79.3
  • Impact: Authorization bypass in path-based interceptors

Commands Used

go get google.golang.org/grpc@v1.79.3
go mod tidy
go mod vendor

Test Plan

  • go build ./... passes
  • Unit tests pass
  • CI green
  • QE verification

Related

🤖 Generated with Claude Code

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
Copy link
Copy Markdown

coderabbitai Bot commented May 7, 2026

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: 3d38dd3d-5fb3-47fd-bded-1b7189afa4ae

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@rh-soboh
Copy link
Copy Markdown
Author

rh-soboh commented May 7, 2026

/ok-to-test

@openshift-ci openshift-ci Bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label May 7, 2026
@openshift-ci openshift-ci Bot requested review from RadekManak and nrb May 7, 2026 08:40
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 7, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

@rh-soboh
Copy link
Copy Markdown
Author

rh-soboh commented May 7, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 7, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@rh-soboh: This pull request references Jira Issue OCPBUGS-80749, 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.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-83913 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-83913 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • 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.

@rh-soboh
Copy link
Copy Markdown
Author

rh-soboh commented May 7, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@rh-soboh: This pull request references Jira Issue OCPBUGS-80749, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-83913 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-83913 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • 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.

@rh-soboh
Copy link
Copy Markdown
Author

rh-soboh commented May 7, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@rh-soboh: This pull request references Jira Issue OCPBUGS-80749, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-83913 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-83913 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @rissh

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 openshift-ci Bot requested a review from rissh May 7, 2026 12:04
@rh-soboh
Copy link
Copy Markdown
Author

rh-soboh commented May 7, 2026

/test e2e-vsphere-staticip-ipam-ovn

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 7, 2026

@rh-soboh: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants