Skip to content

OCPBUGS-103481: CVE-2026-33814-4-18 openshift4/ose-monitoring-plugin-rhel9: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame [openshift-4.18] - #1217

Open
tonyxrmdavidson wants to merge 1 commit into
openshift:release-4.18from
tonyxrmdavidson:OCPBUGS-103481-CVE-2026-33814-4-18
Open

OCPBUGS-103481: CVE-2026-33814-4-18 openshift4/ose-monitoring-plugin-rhel9: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame [openshift-4.18]#1217
tonyxrmdavidson wants to merge 1 commit into
openshift:release-4.18from
tonyxrmdavidson:OCPBUGS-103481-CVE-2026-33814-4-18

Conversation

@tonyxrmdavidson

Copy link
Copy Markdown

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 the pre-replace golang.org/x/net version as 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; go test ./pkg/... -v passes all tests (no test-backend Makefile target on this branch).

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

…rhel9: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame [openshift-4.18]

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 the pre-replace golang.org/x/net version as 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; go test ./pkg/... -v passes all tests (no test-backend Makefile target on this branch).

Backend-only change (Go module dependency), no application code modified. Target branch: release-4.18.
@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-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: 67b43333-40e1-4d33-8da2-b5011e1a7efd

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

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

  • expected dependent Jira Issue OCPBUGS-103703 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 the pre-replace golang.org/x/net version as 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; go test ./pkg/... -v passes all tests (no test-backend Makefile target on this branch).

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

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
openshift-ci Bot requested review from jgbernalp and zhuje September 1, 2026 11:05
@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tonyxrmdavidson
Once this PR has been reviewed and has the lgtm label, please assign jgbernalp 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:

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

Copy link
Copy Markdown
Contributor

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

@jgbernalp

Copy link
Copy Markdown
Contributor

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants