OCPBUGS-103912: CVE-2026-33814-4-20 openshift4/ose-monitoring-plugin-rhel9: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame [openshift-4.20]

[tonyxrmdavidson]

golang.org/x/net's HTTP/2 implementation is vulnerable to a denial-of-service attack (CVE-2026-33814). A malicious or malformed peer can send an HTTP/2 SETTINGS frame with an invalid/out-of-range SETTINGS_MAX_FRAME_SIZE value. The affected code fails to properly validate this setting before using it to size internal buffers/frame handling, allowing a remote peer to trigger excessive resource consumption or a crash in the server, resulting in denial of service.

Fix: added a replace directive in go.mod (replace golang.org/x/net => github.com/openshift-sustaining/net v0.50.0-sec.4) swapping upstream golang.org/x/net for a patched fork that backports the upstream fix for CVE-2026-33814. The require block still lists golang.org/x/net v0.49.0 // indirect; this is expected, as replace unconditionally overrides that at build time (confirmed via go list -m golang.org/x/net, which resolves to the patched fork). go.sum updated with corresponding checksums.

Testing: make build-backend builds successfully against the patched module; make test-backend passes all tests in ./pkg/....

Backend-only change (Go module dependency), no application code modified. Target branch: release-4.20.

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

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-103912, which is invalid:

• expected dependent Jira Issue OCPBUGS-104124 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

golang.org/x/net's HTTP/2 implementation is vulnerable to a denial-of-service attack (CVE-2026-33814). A malicious or malformed peer can send an HTTP/2 SETTINGS frame with an invalid/out-of-range SETTINGS_MAX_FRAME_SIZE value. The affected code fails to properly validate this setting before using it to size internal buffers/frame handling, allowing a remote peer to trigger excessive resource consumption or a crash in the server, resulting in denial of service.

Fix: added a replace directive in go.mod (replace golang.org/x/net => github.com/openshift-sustaining/net v0.50.0-sec.4) swapping upstream golang.org/x/net for a patched fork that backports the upstream fix for CVE-2026-33814. The require block still lists golang.org/x/net v0.49.0 // indirect; this is expected, as replace unconditionally overrides that at build time (confirmed via go list -m golang.org/x/net, which resolves to the patched fork). go.sum updated with corresponding checksums.

Testing: make build-backend builds successfully against the patched module; make test-backend passes all tests in ./pkg/....

Backend-only change (Go module dependency), no application code modified. Target branch: release-4.20.

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

Run ID: 549dd3a6-5d21-4e4e-b456-165c8e0ddcd4

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

[jgbernalp]

/hold

[jgbernalp]

/lgtm
/label qe-approved

[openshift-ci-robot]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-103912, which is invalid:

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

Details

In response to this:

golang.org/x/net's HTTP/2 implementation is vulnerable to a denial-of-service attack (CVE-2026-33814). A malicious or malformed peer can send an HTTP/2 SETTINGS frame with an invalid/out-of-range SETTINGS_MAX_FRAME_SIZE value. The affected code fails to properly validate this setting before using it to size internal buffers/frame handling, allowing a remote peer to trigger excessive resource consumption or a crash in the server, resulting in denial of service.

Fix: added a replace directive in go.mod (replace golang.org/x/net => github.com/openshift-sustaining/net v0.50.0-sec.4) swapping upstream golang.org/x/net for a patched fork that backports the upstream fix for CVE-2026-33814. The require block still lists golang.org/x/net v0.49.0 // indirect; this is expected, as replace unconditionally overrides that at build time (confirmed via go list -m golang.org/x/net, which resolves to the patched fork). go.sum updated with corresponding checksums.

Testing: make build-backend builds successfully against the patched module; make test-backend passes all tests in ./pkg/....

Backend-only change (Go module dependency), no application code modified. Target branch: release-4.20.

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 APPROVED

This pull-request has been approved by: jgbernalp, tonyxrmdavidson

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:

• OWNERS [jgbernalp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jgbernalp]

/unhold

[tonyxrmdavidson]

/jira refresh

[openshift-ci-robot]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-103912, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-104124 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-104124 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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]

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

[openshift-ci-robot]

@tonyxrmdavidson: Jira Issue OCPBUGS-103912: All pull requests linked via external trackers have merged:

• openshift/monitoring-plugin#1215

Jira Issue OCPBUGS-103912 has been moved to the MODIFIED state.

Details

In response to this:

golang.org/x/net's HTTP/2 implementation is vulnerable to a denial-of-service attack (CVE-2026-33814). A malicious or malformed peer can send an HTTP/2 SETTINGS frame with an invalid/out-of-range SETTINGS_MAX_FRAME_SIZE value. The affected code fails to properly validate this setting before using it to size internal buffers/frame handling, allowing a remote peer to trigger excessive resource consumption or a crash in the server, resulting in denial of service.

Fix: added a replace directive in go.mod (replace golang.org/x/net => github.com/openshift-sustaining/net v0.50.0-sec.4) swapping upstream golang.org/x/net for a patched fork that backports the upstream fix for CVE-2026-33814. The require block still lists golang.org/x/net v0.49.0 // indirect; this is expected, as replace unconditionally overrides that at build time (confirmed via go list -m golang.org/x/net, which resolves to the patched fork). go.sum updated with corresponding checksums.

Testing: make build-backend builds successfully against the patched module; make test-backend passes all tests in ./pkg/....

Backend-only change (Go module dependency), no application code modified. Target branch: release-4.20.

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.