Skip to content

OCPBUGS-86189: [release-4.22] OCPBUGS-83943: Bump gRPC to v1.79.3 to resolve CVE-2026-33186#185

Merged
openshift-merge-bot[bot] merged 3 commits into
openshift:release-4.22from
bentito:backport-4.22
May 19, 2026
Merged

OCPBUGS-86189: [release-4.22] OCPBUGS-83943: Bump gRPC to v1.79.3 to resolve CVE-2026-33186#185
openshift-merge-bot[bot] merged 3 commits into
openshift:release-4.22from
bentito:backport-4.22

Conversation

@bentito
Copy link
Copy Markdown

@bentito bentito commented May 19, 2026

Cherry-pick of #183 to release-4.22.

@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 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@bentito: This pull request references Jira Issue OCPBUGS-83943, which is invalid:

  • expected the vulnerability to target either version "4.22." or "openshift-4.22.", but it targets "5.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
  • 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 Jira Issue OCPBUGS-83943 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

Cherry-pick of #183 to release-4.22.

/jira cherrypick OCPBUGS-83943

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 19, 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: 94887315-6ba6-482b-ba97-723ecd110a87

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.

@bentito
Copy link
Copy Markdown
Author

bentito commented May 19, 2026

/jira cherrypick OCPBUGS-83943

@openshift-ci openshift-ci Bot requested review from Thealisyed and rfredette May 19, 2026 15:05
@openshift-ci-robot
Copy link
Copy Markdown

@bentito: Jira Issue OCPBUGS-83943 has been cloned as Jira Issue OCPBUGS-86189. Will retitle bug to link to clone.
/retitle OCPBUGS-86189: [release-4.22] OCPBUGS-83943: Bump gRPC to v1.79.3 to resolve CVE-2026-33186

Details

In response to this:

/jira cherrypick OCPBUGS-83943

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 changed the title [release-4.22] OCPBUGS-83943: Bump gRPC to v1.79.3 to resolve CVE-2026-33186 OCPBUGS-86189: [release-4.22] OCPBUGS-83943: Bump gRPC to v1.79.3 to resolve CVE-2026-33186 May 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@bentito: This pull request references Jira Issue OCPBUGS-86189, 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-83943 to target a version in 5.0.0, but it targets "5.0" 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:

Cherry-pick of #183 to release-4.22.

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

openshift-ci Bot commented May 19, 2026

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

@rikatz
Copy link
Copy Markdown
Member

rikatz commented May 19, 2026

/lgtm
/approve
thanks!

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 19, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz

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 May 19, 2026
@candita
Copy link
Copy Markdown

candita commented May 19, 2026

Fix for CVE was requested to be prioritized for 4.22.
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 19, 2026
@candita
Copy link
Copy Markdown

candita commented May 19, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@candita: This pull request references Jira Issue OCPBUGS-86189, 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-83943 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) 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.

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.

@candita
Copy link
Copy Markdown

candita commented May 19, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@candita: This pull request references Jira Issue OCPBUGS-86189, which is invalid:

  • expected dependent Jira Issue OCPBUGS-83943 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) 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.

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.

@candita
Copy link
Copy Markdown

candita commented May 19, 2026

/jira refresh

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

@candita: This pull request references Jira Issue OCPBUGS-86189, 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.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-83943 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-83943 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
  • bug has dependents
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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 19, 2026
@rhamini3
Copy link
Copy Markdown

marking bug as pre-merge-verified

% oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.22.0-0-2026-05-19-203440-test-ci-ln-gsptj7k-latest   True        False         12m     Cluster version is 4.22.0-0-2026-05-19-203440-test-ci-ln-gsptj7k-latest
iamin@iamin-mac ~ % oc -n openshift-dns get pods
NAME                  READY   STATUS    RESTARTS   AGE
dns-default-lqqzn     2/2     Running   0          24m
dns-default-qf9cq     2/2     Running   0          36m
dns-default-qpmc7     2/2     Running   0          37m
dns-default-rszc7     2/2     Running   0          37m
dns-default-sbrwq     2/2     Running   0          29m
dns-default-sxjnp     2/2     Running   0          30m
node-resolver-5xhbg   1/1     Running   0          37m
node-resolver-dzxwl   1/1     Running   0          25m
node-resolver-ngpt6   1/1     Running   0          31m
node-resolver-plwz6   1/1     Running   0          37m
node-resolver-vb2hr   1/1     Running   0          30m
node-resolver-wn4x5   1/1     Running   0          37m
iamin@iamin-mac ~ % oc rsync -n openshift-dns dns-default-lqqzn:/usr/bin/coredns .
Transfer starting: 1 files
coredns

sent 38 bytes  received 112257160 bytes  1122571980000 bytes/sec
total size is 112229672  speedup is 1.00
Defaulted container "dns" out of: dns, kube-rbac-proxy
iamin@iamin-mac ~ % strings ./coredns >> coredns.txt
iamin@iamin-mac ~ % grep -B1 "v1.17.7" coredns.txt
github.com/expr-lang/expr
v1.17.7
--
github.com/expr-lang/expr
v1.17.7
iamin@iamin-mac ~ % grep -B1 "v0.50.0" coredns.txt
golang.org/x/crypto
v0.50.0
--
golang.org/x/crypto
v0.50.0
iamin@iamin-mac ~ % grep -B1 "v0.43.0" coredns.txt
golang.org/x/sys
v0.43.0
--
golang.org/x/sys
v0.43.0
iamin@iamin-mac ~ % grep -B1 "v1.79.3" coredns.txt
google.golang.org/grpc
v1.79.3
--
google.golang.org/grpc
v1.79.3
iamin@iamin-mac ~ % grep -B1 "v1.2.1" coredns.txt
go.opentelemetry.io/auto/sdk
v1.2.1
--
go.opentelemetry.io/auto/sdk
v1.2.1
iamin@iamin-mac ~ % grep -B1 "v1.39.0" coredns.txt
go.opentelemetry.io/otel
v1.39.0
--
go.opentelemetry.io/otel/metric
v1.39.0
go.opentelemetry.io/otel/sdk
v1.39.0
go.opentelemetry.io/otel/trace
v1.39.0
--
go.opentelemetry.io/otel
v1.39.0
--
go.opentelemetry.io/otel/metric
v1.39.0
go.opentelemetry.io/otel/sdk
v1.39.0
go.opentelemetry.io/otel/trace
v1.39.0
iamin@iamin-mac ~ % grep -B1 "v0.34.0" coredns.txt
golang.org/x/mod
v0.34.0
--
golang.org/x/oauth2
v0.34.0
--
golang.org/x/mod
v0.34.0
--
golang.org/x/oauth2
v0.34.0
iamin@iamin-mac ~ % grep -B1 "v0.53.0" coredns.txt
golang.org/x/net
v0.53.0
--
golang.org/x/net
v0.53.0
iamin@iamin-mac ~ % grep -B1 "v0.42.0" coredns.txt
golang.org/x/term
v0.42.0
--
golang.org/x/term
v0.42.0
iamin@iamin-mac ~ % grep -B1 "v0.36.0" coredns.txt
golang.org/x/text
v0.36.0
--
golang.org/x/text
v0.36.0
iamin@iamin-mac ~ % grep -B1 "v0.43.0" coredns.txt
golang.org/x/sys
v0.43.0
--
golang.org/x/sys
v0.43.0

/verified by @rhamini3

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@rhamini3: This PR has been marked as verified by @rhamini3.

Details

In response to this:

marking bug as pre-merge-verified

% oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.22.0-0-2026-05-19-203440-test-ci-ln-gsptj7k-latest   True        False         12m     Cluster version is 4.22.0-0-2026-05-19-203440-test-ci-ln-gsptj7k-latest
iamin@iamin-mac ~ % oc -n openshift-dns get pods
NAME                  READY   STATUS    RESTARTS   AGE
dns-default-lqqzn     2/2     Running   0          24m
dns-default-qf9cq     2/2     Running   0          36m
dns-default-qpmc7     2/2     Running   0          37m
dns-default-rszc7     2/2     Running   0          37m
dns-default-sbrwq     2/2     Running   0          29m
dns-default-sxjnp     2/2     Running   0          30m
node-resolver-5xhbg   1/1     Running   0          37m
node-resolver-dzxwl   1/1     Running   0          25m
node-resolver-ngpt6   1/1     Running   0          31m
node-resolver-plwz6   1/1     Running   0          37m
node-resolver-vb2hr   1/1     Running   0          30m
node-resolver-wn4x5   1/1     Running   0          37m
iamin@iamin-mac ~ % oc rsync -n openshift-dns dns-default-lqqzn:/usr/bin/coredns .
Transfer starting: 1 files
coredns

sent 38 bytes  received 112257160 bytes  1122571980000 bytes/sec
total size is 112229672  speedup is 1.00
Defaulted container "dns" out of: dns, kube-rbac-proxy
iamin@iamin-mac ~ % strings ./coredns >> coredns.txt
iamin@iamin-mac ~ % grep -B1 "v1.17.7" coredns.txt
github.com/expr-lang/expr
v1.17.7
--
github.com/expr-lang/expr
v1.17.7
iamin@iamin-mac ~ % grep -B1 "v0.50.0" coredns.txt
golang.org/x/crypto
v0.50.0
--
golang.org/x/crypto
v0.50.0
iamin@iamin-mac ~ % grep -B1 "v0.43.0" coredns.txt
golang.org/x/sys
v0.43.0
--
golang.org/x/sys
v0.43.0
iamin@iamin-mac ~ % grep -B1 "v1.79.3" coredns.txt
google.golang.org/grpc
v1.79.3
--
google.golang.org/grpc
v1.79.3
iamin@iamin-mac ~ % grep -B1 "v1.2.1" coredns.txt
go.opentelemetry.io/auto/sdk
v1.2.1
--
go.opentelemetry.io/auto/sdk
v1.2.1
iamin@iamin-mac ~ % grep -B1 "v1.39.0" coredns.txt
go.opentelemetry.io/otel
v1.39.0
--
go.opentelemetry.io/otel/metric
v1.39.0
go.opentelemetry.io/otel/sdk
v1.39.0
go.opentelemetry.io/otel/trace
v1.39.0
--
go.opentelemetry.io/otel
v1.39.0
--
go.opentelemetry.io/otel/metric
v1.39.0
go.opentelemetry.io/otel/sdk
v1.39.0
go.opentelemetry.io/otel/trace
v1.39.0
iamin@iamin-mac ~ % grep -B1 "v0.34.0" coredns.txt
golang.org/x/mod
v0.34.0
--
golang.org/x/oauth2
v0.34.0
--
golang.org/x/mod
v0.34.0
--
golang.org/x/oauth2
v0.34.0
iamin@iamin-mac ~ % grep -B1 "v0.53.0" coredns.txt
golang.org/x/net
v0.53.0
--
golang.org/x/net
v0.53.0
iamin@iamin-mac ~ % grep -B1 "v0.42.0" coredns.txt
golang.org/x/term
v0.42.0
--
golang.org/x/term
v0.42.0
iamin@iamin-mac ~ % grep -B1 "v0.36.0" coredns.txt
golang.org/x/text
v0.36.0
--
golang.org/x/text
v0.36.0
iamin@iamin-mac ~ % grep -B1 "v0.43.0" coredns.txt
golang.org/x/sys
v0.43.0
--
golang.org/x/sys
v0.43.0

/verified by @rhamini3

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-merge-bot openshift-merge-bot Bot merged commit 9a71d9a into openshift:release-4.22 May 19, 2026
9 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@bentito: Jira Issue Verification Checks: Jira Issue OCPBUGS-86189
✔️ 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-86189 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:

Cherry-pick of #183 to release-4.22.

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants