[release-4.22] OCPBUGS-102055: Bump golang.org/x/net to v0.53.0 for CVE-2026-33814

[atewari-rh]

Summary

This PR addresses CVE-2026-33814 by bumping golang.org/x/net from v0.49.0 to v0.53.0 on release-4.22. The patched HTTP/2 client rejects SETTINGS_MAX_FRAME_SIZE=0 instead of looping on CONTINUATION writes.

Changes

• Updated golang.org/x/net from v0.49.0 to v0.53.0
• Ran go mod tidy and go mod vendor
• Go version unchanged at 1.25.0

CVE Details

CVE-2026-33814 / GO-2026-4918: HTTP/2 client infinite loop DoS when a peer sends SETTINGS_MAX_FRAME_SIZE=0.

• Severity: Important
• Affected: golang.org/x/net/http2 < v0.53.0
• Fix: processSettingsNoWrite now validates all SETTINGS via Setting.Valid() (rejects MAX_FRAME_SIZE < 16384)

Stdlib net/http is separately listed as fixed in Go 1.25.10 / 1.26.3. This PR covers the vendored x/net client path; golang-builder rebase is still needed for stdlib.

Test Plan

• Go version unchanged (go 1.25.0)
• Vendored processSettingsNoWrite calls s.Valid() before applying SettingMaxFrameSize
• Unit tests / CI
• QE verification

Related

• Jira: OCPBUGS-102055
• Go Vuln DB: GO-2026-4918

[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

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-104438 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New 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 addresses CVE-2026-33814 by bumping golang.org/x/net from v0.49.0 to v0.53.0 on release-4.22. The patched HTTP/2 client rejects SETTINGS_MAX_FRAME_SIZE=0 instead of looping on CONTINUATION writes.

Changes

• Updated golang.org/x/net from v0.49.0 to v0.53.0
• Ran go mod tidy and go mod vendor
• Go version unchanged at 1.25.0

CVE Details

CVE-2026-33814 / GO-2026-4918: HTTP/2 client infinite loop DoS when a peer sends SETTINGS_MAX_FRAME_SIZE=0.

• Severity: Important
• Affected: golang.org/x/net/http2 < v0.53.0
• Fix: processSettingsNoWrite now validates all SETTINGS via Setting.Valid() (rejects MAX_FRAME_SIZE < 16384)

Stdlib net/http is separately listed as fixed in Go 1.25.10 / 1.26.3. This PR covers the vendored x/net client path; golang-builder rebase is still needed for stdlib.

Test Plan

• Go version unchanged (go 1.25.0)
• Vendored processSettingsNoWrite calls s.Valid() before applying SettingMaxFrameSize
• Unit tests / CI
• QE verification

Related

• Jira: OCPBUGS-102055
• Go Vuln DB: GO-2026-4918

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: Pro Plus

Run ID: 351ddef7-0427-44ba-82bf-aa9671ab6d64

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

---

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.}

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

[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 joelspeed 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

[atewari-rh]

/ok-to-test

[openshift-ci]

@atewari-rh: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/ok-to-test

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.