[release-4.19] OCPBUGS-92919,OCPBUGS-89936: Replace golang.org/x/crypto with github.com/openshift-sustaining/[email protected]

[sunku5494]

address CVE-2026-39829, CVE-2026-46597

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[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: 351e5afb-2a63-4be6-9b9e-b9a0f01af4f7

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

@sunku5494: This pull request references Jira Issue OCPBUGS-92919, which is invalid:

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

This pull request references Jira Issue OCPBUGS-89936, which is invalid:

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

address CVE-2026-39829, CVE-2026-46597

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

[sunku5494]

/test images

[prabhapa]

/label backport-risk-assessed
/lgtm

[openshift-ci]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn

[sunku5494]

/test e2e-aws-ovn

[sunku5494]

/test e2e-aws-ovn

[openshift-ci]

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

[tthvo]

Hello @sunku5494, I also see a similar PR #10840, which bumps to a (higher?) patch version v0.41.0-sec.4.

Could you tell us which one we are going forward with?

[sunku5494]

Hello @sunku5494, I also see a similar PR #10840, which bumps to a (higher?) patch version v0.41.0-sec.4.

Could you tell us which one we are going forward with?

We are following a practice to choose the patch version that only fixes the attached CVE bug ids. due to this, we are seeing multiple PR's created with different patch version. At this time, we have seen a couple of them as there are many CVE's reported for crypto during the same period. So, I see this is an expected behavior and could consider this for merge. we will try to work on the ways to see if we could avoid this in future. Thanks