Fix for OCPBUGS-88167: CVE-2026-39821

[germanparente]

Summary

• Fixes CVE-2026-39821 (golang.org/x/net/idna Punycode validation bypass, CVSS 9.6) on release-4.15
• Uses go mod edit -replace to pin golang.org/x/net to github.com/openshift-sustaining/net@v0.35.0-sec.2
• Ran go mod tidy, go mod vendor, and verified clean build with go build ./...

Test plan

• go build ./... passes locally
• CI passes

🤖 Generated with Claude Code

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

@germanparente: This pull request references Jira Issue OCPBUGS-88167, which is invalid:

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

• Fixes CVE-2026-39821 (golang.org/x/net/idna Punycode validation bypass, CVSS 9.6) on release-4.15
• Uses go mod edit -replace to pin golang.org/x/net to github.com/openshift-sustaining/net@v0.35.0-sec.2
• Ran go mod tidy, go mod vendor, and verified clean build with go build ./...

Test plan

• go build ./... passes locally
• CI passes

🤖 Generated with Claude Code

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

Run ID: 4a936d82-0c9d-4c71-b75e-be9671ccb282

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@germanparente: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/verify	33e8fc5	link	true	/test verify
ci/prow/images	33e8fc5	link	true	/test images
ci/prow/rpm-build	33e8fc5	link	true	/test rpm-build
ci/prow/security	33e8fc5	link	false	/test security
ci/prow/verify-deps	33e8fc5	link	true	/test verify-deps
ci/prow/build-rpms-from-tar	33e8fc5	link	true	/test build-rpms-from-tar
ci/prow/unit	33e8fc5	link	true	/test unit

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.