[release-4.13] OCPBUGS-86877: Bump google.golang.org/grpc

[rhdmalone]

Step 1 — Add the grpc replace directive:

go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.64.1-sec.1
Step 2 — Pre-fetch the sustaining fork to populate go.sum:

go mod download github.com/openshift-sustaining/grpc-go@v1.64.1-sec.1
Step 3 — Tidy with error tolerance (OTel module restructuring causes unavoidable warnings):

go mod tidy -e
Step 4 — Manually update go.mod to align OTel exporter versions with the OTel core (v1.24.0):

go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.11.2 → v1.24.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.11.2 → v1.24.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.11.2 → v1.24.0
go.opentelemetry.io/otel/sdk v1.22.0 → v1.24.0
Remove go.opentelemetry.io/otel/exporters/otlp/internal/retry v1.11.2 (no longer a separate module at v1.24.0)
Step 5 — Tidy again to update go.sum for the new OTel versions:

go mod tidy -e
Step 6 — Update the vendor directory:

go mod vendor
Step 7 — Update semconv in tracing/tracing.go:

Change semconv "go.opentelemetry.io/otel/semconv/v1.12.0" → semconv "go.opentelemetry.io/otel/semconv/v1.24.0"
Step 8 — Re-vendor to pick up the semconv change:

go mod vendor
Step 9 — Commit:

git add go.mod go.sum vendor/ tracing/tracing.go
git commit -m "CVE-2026-33186: fix grpc authorization bypass on release-4.13

• Replace google.golang.org/grpc with openshift-sustaining/grpc-go v1.64.1-sec.1
• Bump go.opentelemetry.io/otel exporters and SDK from v1.11.2/v1.22.0 to v1.24.0
  to resolve module restructuring incompatibility with OTel core v1.24.0
• Remove deprecated go.opentelemetry.io/otel/exporters/otlp/internal/retry module
• Update tracing semconv from v1.12.0 to v1.24.0 to avoid schema URL conflicts"

[openshift-ci-robot]

@rhdmalone: This pull request references Jira Issue OCPBUGS-86877, 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 Jira Issue OCPBUGS-86877 to depend on a bug targeting a version in 4.14.0, 4.14.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Step 1 — Add the grpc replace directive:

go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.64.1-sec.1
Step 2 — Pre-fetch the sustaining fork to populate go.sum:

go mod download github.com/openshift-sustaining/grpc-go@v1.64.1-sec.1
Step 3 — Tidy with error tolerance (OTel module restructuring causes unavoidable warnings):

go mod tidy -e
Step 4 — Manually update go.mod to align OTel exporter versions with the OTel core (v1.24.0):

go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.11.2 → v1.24.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.11.2 → v1.24.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.11.2 → v1.24.0
go.opentelemetry.io/otel/sdk v1.22.0 → v1.24.0
Remove go.opentelemetry.io/otel/exporters/otlp/internal/retry v1.11.2 (no longer a separate module at v1.24.0)
Step 5 — Tidy again to update go.sum for the new OTel versions:

go mod tidy -e
Step 6 — Update the vendor directory:

go mod vendor
Step 7 — Update semconv in tracing/tracing.go:

Change semconv "go.opentelemetry.io/otel/semconv/v1.12.0" → semconv "go.opentelemetry.io/otel/semconv/v1.24.0"
Step 8 — Re-vendor to pick up the semconv change:

go mod vendor
Step 9 — Commit:

git add go.mod go.sum vendor/ tracing/tracing.go
git commit -m "CVE-2026-33186: fix grpc authorization bypass on release-4.13

• Replace google.golang.org/grpc with openshift-sustaining/grpc-go v1.64.1-sec.1
• Bump go.opentelemetry.io/otel exporters and SDK from v1.11.2/v1.22.0 to v1.24.0
  to resolve module restructuring incompatibility with OTel core v1.24.0
• Remove deprecated go.opentelemetry.io/otel/exporters/otlp/internal/retry module
• Update tracing semconv from v1.12.0 to v1.24.0 to avoid schema URL conflicts"

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: 841fcaaa-0709-4473-9e0b-963c45948e70

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

[simonpasquier]

/label backport-risk-assessed

[simonpasquier]

/approve
/jira refresh

[openshift-ci-robot]

@simonpasquier: This pull request references Jira Issue OCPBUGS-86877, 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 Jira Issue OCPBUGS-86877 to depend on a bug targeting a version in 4.14.0, 4.14.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

Details

In response to this:

/approve
/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.

[simonpasquier]

/retest-required
/jira refresh

[openshift-ci-robot]

@simonpasquier: This pull request references Jira Issue OCPBUGS-86877, 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 Jira Issue OCPBUGS-86877 to depend on a bug targeting a version in 4.14.0, 4.14.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

Details

In response to this:

/retest-required
/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.

[simonpasquier]

/jira refresh

[openshift-ci-robot]

@simonpasquier: This pull request references Jira Issue OCPBUGS-86877, which is invalid:

• expected dependent Jira Issue OCPBUGS-86878 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.

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.

[simonpasquier]

/verified by @simonpasquier
/lgtm

[openshift-ci-robot]

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

Details

In response to this:

/verified by @simonpasquier
/lgtm

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 APPROVED

This pull-request has been approved by: rhdmalone, simonpasquier

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:

• OWNERS [simonpasquier]

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

[rhdmalone]

/test e2e-agnostic-cmo

[openshift-ci]

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