OCPBUGS-86884:[release-4.13] bump google.golang.org/grpc to v1.64.1-sec.1

[AkashMore08]

Address CVE-2026-33186 via transitive dependency update

This PR resolves CVE-2026-33186 for release-4.13 by replacing google.golang.org/grpc with github.com/openshift-sustaining/grpc-go@v1.64.1-sec.1, a patched fork containing security fixes equivalent to upstream v1.79.3.

Along with the CVE fix, we had to manually bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc to v1.17.0.

Why otlptracegrpc was bumped to v1.17.0?

Replacing google.golang.org/grpc with v1.64.1-sec.1 changes the module graph the new grpc version requires higher minimum versions of shared dependencies (google.golang.org/protobuf v1.33.0, golang.org/x/net v0.26.0, etc.). This forces go mod tidy to re-resolve the entire dependency tree, which exposes a pre-existing broken module resolution in otlptracegrpc v1.10.0 through v1.16.0.

These versions depend on internal packages (go.opentelemetry.io/otel/exporters/otlp/internal, go.opentelemetry.io/otel/exporters/otlp/internal/envconfig) that were resolved via local replace directives within the OpenTelemetry monorepo during development. When consumed from the Go module proxy, those local replaces are ignored, and go mod tidy fails because the enclosing module (go.opentelemetry.io/otel/exporters/otlp@v0.20.1) does not contain these packages.

otlptracegrpc v1.17.0 is the first version that inlined these internal packages and removed the broken external module dependency. This bump then transitively upgrades otelgrpc (from v0.35.0 to v0.49.0), the core otel SDK, and other shared dependencies are auto-resolved by go mod tidy.

[openshift-ci-robot]

@AkashMore08: This pull request references Jira Issue OCPBUGS-86884, which is invalid:

• expected Jira Issue OCPBUGS-86884 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:

Address CVE-2026-33186 via transitive dependency update

This PR resolves CVE-2026-33186 for release-4.13 by replacing google.golang.org/grpc with github.com/openshift-sustaining/grpc-go@v1.64.1-sec.1, a patched fork containing security fixes equivalent to upstream v1.79.3.

Along with the CVE fix, we had to manually bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc to v1.17.0.

Why otlptracegrpc was bumped to v1.17.0?

Replacing google.golang.org/grpc with v1.64.1-sec.1 changes the module graph the new grpc version requires higher minimum versions of shared dependencies (google.golang.org/protobuf v1.33.0, golang.org/x/net v0.26.0, etc.). This forces go mod tidy to re-resolve the entire dependency tree, which exposes a pre-existing broken module resolution in otlptracegrpc v1.10.0 through v1.16.0.

These versions depend on internal packages (go.opentelemetry.io/otel/exporters/otlp/internal, go.opentelemetry.io/otel/exporters/otlp/internal/envconfig) that were resolved via local replace directives within the OpenTelemetry monorepo during development. When consumed from the Go module proxy, those local replaces are ignored, and go mod tidy fails because the enclosing module (go.opentelemetry.io/otel/exporters/otlp@v0.20.1) does not contain these packages.

otlptracegrpc v1.17.0 is the first version that inlined these internal packages and removed the broken external module dependency. This bump then transitively upgrades otelgrpc (from v0.35.0 to v0.49.0), the core otel SDK, and other shared dependencies are auto-resolved by go mod tidy.

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: e1434ae1-2b6e-4eab-b8ab-f0a80362006a

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]

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

[prabhapa]

/lgtm
/label backport-risk-assessed
/label approved
/verified by CI

[openshift-ci-robot]

@prabhapa: This PR has been marked as verified by CI.

Details

In response to this:

/lgtm
/label backport-risk-assessed
/label approved
/verified by CI

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: AkashMore08, prabhapa
Once this PR has been reviewed and has the lgtm label, please assign bparees 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

[AkashMore08]

/jira refresh

[openshift-ci-robot]

@AkashMore08: This pull request references Jira Issue OCPBUGS-86884, which is invalid:

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

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.

[prabhapa]

/label approved

[AkashMore08]

/jira refresh

[openshift-ci-robot]

@AkashMore08: This pull request references Jira Issue OCPBUGS-86884, which is invalid:

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

[AkashMore08]

/jira refresh

[openshift-ci-robot]

@AkashMore08: This pull request references Jira Issue OCPBUGS-86884, 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.13.z) matches configured target version for branch (4.13.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-86883 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-86883 targets the "4.14.z" version, which is one of the valid target versions: 4.14.0, 4.14.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.

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]

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

Address CVE-2026-33186 via transitive dependency update

This PR resolves CVE-2026-33186 for release-4.13 by replacing google.golang.org/grpc with github.com/openshift-sustaining/grpc-go@v1.64.1-sec.1, a patched fork containing security fixes equivalent to upstream v1.79.3.

Along with the CVE fix, we had to manually bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc to v1.17.0.

Why otlptracegrpc was bumped to v1.17.0?

Replacing google.golang.org/grpc with v1.64.1-sec.1 changes the module graph the new grpc version requires higher minimum versions of shared dependencies (google.golang.org/protobuf v1.33.0, golang.org/x/net v0.26.0, etc.). This forces go mod tidy to re-resolve the entire dependency tree, which exposes a pre-existing broken module resolution in otlptracegrpc v1.10.0 through v1.16.0.

These versions depend on internal packages (go.opentelemetry.io/otel/exporters/otlp/internal, go.opentelemetry.io/otel/exporters/otlp/internal/envconfig) that were resolved via local replace directives within the OpenTelemetry monorepo during development. When consumed from the Go module proxy, those local replaces are ignored, and go mod tidy fails because the enclosing module (go.opentelemetry.io/otel/exporters/otlp@v0.20.1) does not contain these packages.

otlptracegrpc v1.17.0 is the first version that inlined these internal packages and removed the broken external module dependency. This bump then transitively upgrades otelgrpc (from v0.35.0 to v0.49.0), the core otel SDK, and other shared dependencies are auto-resolved by go mod tidy.

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-robot]

Fix included in release 4.13.0-0.nightly-2026-07-10-115340