Skip to content

DFBUGS-9295: [release-4.18] switch to openshift-sustaining/net v0.35.0-sec.3 for CVE-2026-33814 - #799

Open
AnikaYadav1 wants to merge 1 commit into
red-hat-storage:release-4.18from
AnikaYadav1:cve-2026-33814-release-4.18
Open

AnikaYadav1 wants to merge 1 commit into
red-hat-storage:release-4.18from
AnikaYadav1:cve-2026-33814-release-4.18

Conversation

@AnikaYadav1

@AnikaYadav1 AnikaYadav1 commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

DFBUGS-9295

Address CVE-2026-33814 (GO-2026-4918), which requires two fixes on ODF 4.18:

  • RHEL Go builder image with the stdlib backport (golang-1.22.12-17.el9), already available
  • Replace golang.org/x/net with github.com/openshift-sustaining/net v0.35.0-sec.3 (this PR)
  • Refresh vendored dependencies via make deps-update.

A patched upstream x/net would force a Go bump on this branch. The sustaining fork applies the fix and keeps the current toolchain.The operator build gets the stdlib fix from the updated RHEL builder image.

CVE-2026-33814 (GO-2026-4918) requires two fixes on this branch:
1. RHEL Go builder image with stdlib backport (golang-1.22.12-17.el9)
2. openshift-sustaining/net v0.35.0-sec.3 via go.mod replace
The builder image fix is already available. This commit adds the
sustaining fork replacement for golang.org/x/net and refreshes vendor.
Ref-DFBUGS-9295

Signed-off-by: AnikaYadav1 <Anika.Yadav1@ibm.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 the referenced jira bug is invalid for the branch this PR is targeting labels Oct 6, 2026
@openshift-ci-robot

openshift-ci-robot commented Oct 6, 2026 •

Copy link
Copy Markdown

@AnikaYadav1: This pull request references [Jira Issue DFBUGS-9295](https://redhat.atlassian.net/browse/DFBUGS-9295), which is invalid:

  • expected the vulnerability to target the "odf-4.18.30" version, but no target version was set

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:

DFBUGS-9295

Address CVE-2026-33814 (GO-2026-4918), which requires two fixes on ODF 4.18:

  • RHEL Go builder image with the stdlib backport (golang-1.22.12-17.el9), already available
  • Replace golang.org/x/net with github.com/openshift-sustaining/net v0.35.0-sec.3 (this PR)
  • Refresh vendored dependencies via make deps-update.

A patched upstream x/net would force a Go bump on this branch. The sustaining fork applies the fix and keeps the current toolchain.The operator build gets the stdlib fix from the updated RHEL builder image.

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.

@leelavg

leelavg commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

/approve
/lgtm

@openshift-ci

openshift-ci Bot commented Oct 7, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AnikaYadav1, leelavg

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 label Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved jira/invalid-bug Indicates that the 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 size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants