[release-4.22] OCPBUGS-101577, OCPBUGS-101576: Address CVE-2026-42502

[ocp-sustaining-admins]

This is an automated PR from the ARC system.

This change addresses CVE-2026-42502 by updating golang.org/x/net/html on branch release-4.22.

Changes were generated using the following commands:

./ $ go1.25.12 get golang.org/x/net/html@v0.55.0
./ $ go1.25.12 mod tidy
./ $ go1.25.12 mod vendor

---

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

/assign @namansharma18899 @UdayYendva

Common PR issues and how to fix them:

1. Title needs to be changed:
   This might be needed if a PR references multiple Jira issues and some of them have been closed as duplicates.

   Use /retitle <NEW TITLE> command from openshift-ci bot

   openshift-ci bot commands

2. verify-commits check is failing:
   Commits need to be in the format UPSTREAM: PR#|<carry>|<drop>: <commit message>.

   You can do achieve this by doing one of the following:

   • Rerunning the ARC Remediation and specifying an Upstream PR Number.
   • Cloning the ARC Fork, using git commit --amend -m <commit message> and force pushing the changes to the fork.

   verify-commits documentation

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

@ocp-sustaining-admins: This pull request references Jira Issue OCPBUGS-101577, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Not a Bug) instead
• expected Jira Issue OCPBUGS-101577 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

This pull request references Jira Issue OCPBUGS-101576, which is invalid:

• expected Jira Issue OCPBUGS-101576 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

This is an automated PR from the ARC system.

This change addresses CVE-2026-42502 by updating golang.org/x/net/html on branch release-4.22.

Changes were generated using the following commands:

./ $ go1.25.12 get golang.org/x/net/html@v0.55.0
./ $ go1.25.12 mod tidy
./ $ go1.25.12 mod vendor

---

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

/assign @namansharma18899 @UdayYendva

Common PR issues and how to fix them:

1. Title needs to be changed:
   This might be needed if a PR references multiple Jira issues and some of them have been closed as duplicates.

   Use /retitle <NEW TITLE> command from openshift-ci bot

   openshift-ci bot commands

2. verify-commits check is failing:
   Commits need to be in the format UPSTREAM: PR#|<carry>|<drop>: <commit message>.

   You can do achieve this by doing one of the following:

   • Rerunning the ARC Remediation and specifying an Upstream PR Number.
   • Cloning the ARC Fork, using git commit --amend -m <commit message> and force pushing the changes to the fork.

   verify-commits documentation

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: c2ff6998-6305-4bd9-9359-a236b5e57cd3

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

Hi @ocp-sustaining-admins. 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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.