OCPBUGS-103693: CVE-2026-33814: Bump golang.org/x/net to openshift-sustaining/net v0.43.0-sec.4 (release-4.19)

[atewari-rh]

Summary

Addresses CVE-2026-33814 (GO-2026-4918) on release-4.19 by updating vendored golang.org/x/net via the OpenShift sustaining fork.

Malicious HTTP/2 servers can trigger an infinite loop in the client transport when sending SETTINGS_MAX_FRAME_SIZE=0 (DoS). Fixed in golang.org/x/net ≥ v0.53.0; sustaining backport provided as github.com/openshift-sustaining/net v0.50.0-sec.4.

Changes

• Add replace golang.org/x/net => github.com/openshift-sustaining/net v0.43.0-sec.4
• Bump golang.org/x/net requirement v0.46.0 → v0.49.0
• Regenerate vendor/ (go mod vendor)
• Update transitive golang.org/x/* dependencies (mod, sync, sys, term, text, tools)

Scope: single module root (go.mod + vendor/ only)

Test plan

• go mod verify
• CGO_ENABLED=0 go build -mod=vendor -o bin/machine-controller-manager ./cmd/manager
• CGO_ENABLED=0 go build -mod=vendor -o bin/termination-handler ./cmd/termination-handler

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

Run ID: 3b147d05-4e90-4066-9bc3-059d0a7c7381

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]

@atewari-rh: This pull request references Jira Issue OCPBUGS-103693, which is invalid:

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

Addresses CVE-2026-33814 (GO-2026-4918) on release-4.19 by updating vendored golang.org/x/net via the OpenShift sustaining fork.

Malicious HTTP/2 servers can trigger an infinite loop in the client transport when sending SETTINGS_MAX_FRAME_SIZE=0 (DoS). Fixed in golang.org/x/net ≥ v0.53.0; sustaining backport provided as github.com/openshift-sustaining/net v0.50.0-sec.4.

Changes

• Add replace golang.org/x/net => github.com/openshift-sustaining/net v0.50.0-sec.4
• Bump golang.org/x/net requirement v0.46.0 → v0.49.0
• Regenerate vendor/ (go mod vendor)
• Update transitive golang.org/x/* dependencies (mod, sync, sys, term, text, tools)

Scope: single module root (go.mod + vendor/ only)

Test plan

• go mod verify
• CGO_ENABLED=0 go build -mod=vendor -o bin/machine-controller-manager ./cmd/manager
• CGO_ENABLED=0 go build -mod=vendor -o bin/termination-handler ./cmd/termination-handler

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

Hi @atewari-rh. Thanks for your PR.

I'm waiting for a openshift 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.

[openshift-ci-robot]

@atewari-rh: This pull request references Jira Issue OCPBUGS-103693, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-103908 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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:

Summary

Addresses CVE-2026-33814 (GO-2026-4918) on release-4.19 by updating vendored golang.org/x/net via the OpenShift sustaining fork.

Malicious HTTP/2 servers can trigger an infinite loop in the client transport when sending SETTINGS_MAX_FRAME_SIZE=0 (DoS). Fixed in golang.org/x/net ≥ v0.53.0; sustaining backport provided as github.com/openshift-sustaining/net v0.50.0-sec.4.

Changes

• Add replace golang.org/x/net => github.com/openshift-sustaining/net v0.43.0-sec.4
• Bump golang.org/x/net requirement v0.46.0 → v0.49.0
• Regenerate vendor/ (go mod vendor)
• Update transitive golang.org/x/* dependencies (mod, sync, sys, term, text, tools)

Scope: single module root (go.mod + vendor/ only)

Test plan

• go mod verify
• CGO_ENABLED=0 go build -mod=vendor -o bin/machine-controller-manager ./cmd/manager
• CGO_ENABLED=0 go build -mod=vendor -o bin/termination-handler ./cmd/termination-handler

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.