[prabhapa]

Summary

This PR replaces golang.org/x/net with github.com/openshift-sustaining/net@v0.35.0-sec.4.

Rationale

CVE-2026-33814, a Go HTTP/2 denial of service caused by a malformed SETTINGS_MAX_FRAME_SIZE frame, is fixed upstream in golang.org/x/net v0.53.0, which requires Go 1.25. The release-4.17 branch is built with Go 1.22 and cannot consume that upstream release. The v0.35.0-sec.4 sustaining fork carries the compatible backport for this Go version.

Source

• Repository: https://github.com/redhat-cne/cloud-event-proxy
• Branch: release-4.17

Jira coverage

This shared source change addresses:

• OCPBUGS-103163 — openshift4/ose-cloud-event-proxy-rhel9

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[openshift-ci-robot]

@prabhapa: This pull request references Jira Issue OCPBUGS-103163, which is invalid:

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

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

Details

In response to this:

Summary

This PR replaces golang.org/x/net with github.com/openshift-sustaining/net@v0.35.0-sec.4.

Rationale

CVE-2026-33814, a Go HTTP/2 denial of service caused by a malformed SETTINGS_MAX_FRAME_SIZE frame, is fixed upstream in golang.org/x/net v0.53.0, which requires Go 1.25. The release-4.17 branch is built with Go 1.22 and cannot consume that upstream release. The v0.35.0-sec.4 sustaining fork carries the compatible backport for this Go version.

Source

• Repository: https://github.com/redhat-cne/cloud-event-proxy
• Branch: release-4.17

Jira coverage

This shared source change addresses:

• OCPBUGS-103163 — openshift4/ose-cloud-event-proxy-rhel9

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

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: cd5391e4-5bc9-4935-bd4d-f3ff847d46e9

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

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

Hi @prabhapa. Thanks for your PR.

I'm waiting for a redhat-cne member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.