Skip to content

[release-4.19] OCPBUGS-103592: CVE-2026-33814: replace golang.org/x/net with openshift-sustaining fork - #611

Open
mariocr73 wants to merge 1 commit into
openshift:release-4.19from
mariocr73:ocpbugs-103592-cve-2026-33814-xnet-replace-fork
Open

[release-4.19] OCPBUGS-103592: CVE-2026-33814: replace golang.org/x/net with openshift-sustaining fork#611
mariocr73 wants to merge 1 commit into
openshift:release-4.19from
mariocr73:ocpbugs-103592-cve-2026-33814-xnet-replace-fork

Conversation

@mariocr73

Copy link
Copy Markdown

Same rationale as OCPBUGS-102919 (release-4.16). Builder pinned to Go 1.23 (rhel-9-golang-1.23-openshift-4.19). Uses replace golang.org/x/net => github.com/openshift-sustaining/net v0.43.0-sec.3 (closer to this branch's current v0.41.0 baseline than v0.35.0-sec.3).

go build/go vet clean; govulncheck confirms GO-2026-4918 no longer reported for ./cmd/azure-disk-csi-driver-operator/....

…ft-sustaining fork

Same rationale/fix as OCPBUGS-102919 (release-4.16): builder is pinned to
Go 1.23 (rhel-9-golang-1.23-openshift-4.19), below the go>=1.25 that
golang.org/x/net@v0.53.0 requires, so uses
`replace golang.org/x/net => github.com/openshift-sustaining/net v0.43.0-sec.3`
(closer to this branch's current v0.41.0 baseline than v0.35.0-sec.3, and its
own go.mod already targets go1.23, matching this branch's toolchain exactly).
go build/go vet clean; govulncheck confirms GO-2026-4918 no longer reported
for ./cmd/azure-disk-csi-driver-operator/...

Co-authored-by: Cursor <cursoragent@cursor.com>
@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 Sep 1, 2026
@coderabbitai

coderabbitai Bot commented Sep 1, 2026

Copy link
Copy Markdown

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: Team

Run ID: 23a6bbb3-35fd-4408-9114-cbd7ef2346fc

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

Copy link
Copy Markdown

@mariocr73: This pull request references Jira Issue OCPBUGS-103592, which is invalid:

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

Same rationale as OCPBUGS-102919 (release-4.16). Builder pinned to Go 1.23 (rhel-9-golang-1.23-openshift-4.19). Uses replace golang.org/x/net => github.com/openshift-sustaining/net v0.43.0-sec.3 (closer to this branch's current v0.41.0 baseline than v0.35.0-sec.3).

go build/go vet clean; govulncheck confirms GO-2026-4918 no longer reported for ./cmd/azure-disk-csi-driver-operator/....

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

Copy link
Copy Markdown
Contributor

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

@openshift-ci
openshift-ci Bot requested review from dobsonj and mandre September 1, 2026 02:46
@dobsonj

dobsonj commented Sep 1, 2026

Copy link
Copy Markdown
Member

/lgtm
/approve
/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 Sep 1, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 1, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-upgrade
/test e2e-azure
/test e2e-azure-csi
/test e2e-azure-file-csi
/test e2e-azure-file-nfs-csi
/test e2e-azure-ovn-upgrade

@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dobsonj, mariocr73

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 Sep 1, 2026
@mariocr73

Copy link
Copy Markdown
Author

/retest

@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

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

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants