[germanparente]

Summary

• Replaces react-linkify (depends on vulnerable linkify-it) with linkify-react + linkifyjs
• Fixes CVE-2026-48801: quadratic algorithmic complexity in LinkifyIt#match scan loop (DoS)
• Backport of OCPBUGS-98879, CONSOLE-5133: Replace react-linkify with linkify-react to fix CVE-2026-48801 #16814 approach to this release branch

[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

[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: 3f1ba18d-7f07-43a0-93a4-57d08542a5d0

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci-robot]

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

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

• Replaces react-linkify (depends on vulnerable linkify-it) with linkify-react + linkifyjs
• Fixes CVE-2026-48801: quadratic algorithmic complexity in LinkifyIt#match scan loop (DoS)
• Backport of OCPBUGS-98879, CONSOLE-5133: Replace react-linkify with linkify-react to fix CVE-2026-48801 #16814 approach to this release branch

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.

[germanparente]

/label backport-risk-assessed

[germanparente]

/jira refresh

[openshift-ci-robot]

@germanparente: This pull request references Jira Issue OCPBUGS-98765, 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.19.z) matches configured target version for branch (4.19.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-98785 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-98785 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.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.

[germanparente]

/verified by CI

[openshift-ci-robot]

@germanparente: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

[germanparente]

/pipeline required

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console

[germanparente]

/test e2e-gcp-console

[germanparente]

/test e2e-gcp-console

[germanparente]

/test e2e-gcp-console

[germanparente]

/test e2e-gcp-console

[germanparente]

The PR replaces react-linkify (which depends on vulnerable linkify-it) with linkify-react + linkifyjs to fix CVE-2026-48801 (quadratic complexity DoS in linkify-it's match scan loop).

Changes look correct:

1. frontend/package.json — Removes react-linkify, adds linkify-react + linkifyjs ^4.2.0, adds Jest mock mapping for the new module
2. frontend/mocks/linkify-react.js — Simple mock for unit tests, renders children in a span
3. frontend/public/components/app.jsx — Removes the old linkify.set({ fuzzyLink: false }) global config (no longer needed since the new library uses explicit URL validation)
4. frontend/public/components/utils/link.tsx — Replaces the react-linkify Linkify component with linkify-react's version. The linkifyOptions config properly:
   • Renders links with target="_blank" and rel="noopener noreferrer" (same behavior as before)
   • Validates URLs to only match https?:// (replaces the old fuzzyLink: false setting)
5. frontend/yarn.lock — Cleanly removes react-linkify, linkify-it, tlds, uc.micro and adds linkify-react + linkifyjs 4.3.3

All CI checks (analyze, backend, frontend, images) passed. The e2e failure is unrelated. PR looks good to merge.

Then:

/override ci/prow/e2e-gcp-console

[openshift-ci]

@germanparente: Overrode contexts on behalf of germanparente: ci/prow/e2e-gcp-console

Details

In response to this:

The PR replaces react-linkify (which depends on vulnerable linkify-it) with linkify-react + linkifyjs to fix CVE-2026-48801 (quadratic complexity DoS in linkify-it's match scan loop).

Changes look correct:

1. frontend/package.json — Removes react-linkify, adds linkify-react + linkifyjs ^4.2.0, adds Jest mock mapping for the new module
2. frontend/mocks/linkify-react.js — Simple mock for unit tests, renders children in a span
3. frontend/public/components/app.jsx — Removes the old linkify.set({ fuzzyLink: false }) global config (no longer needed since the new library uses explicit URL validation)
4. frontend/public/components/utils/link.tsx — Replaces the react-linkify Linkify component with linkify-react's version. The linkifyOptions config properly:

• Renders links with target="_blank" and rel="noopener noreferrer" (same behavior as before)
• Validates URLs to only match https?:// (replaces the old fuzzyLink: false setting)

5. frontend/yarn.lock — Cleanly removes react-linkify, linkify-it, tlds, uc.micro and adds linkify-react + linkifyjs 4.3.3

All CI checks (analyze, backend, frontend, images) passed. The e2e failure is unrelated. PR looks good to merge.

Then:

/override ci/prow/e2e-gcp-console

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.

[prabhapa]

/lgtm
/label approved

[openshift-merge-bot]

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• frontend/OWNERS

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

[germanparente]

as this one has been lgtm'd:

/label approved

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 5a48a95 and 2 for PR HEAD a74e5a8 in total

[openshift-ci]

@germanparente: 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]

@germanparente: Jira Issue Verification Checks: Jira Issue OCPBUGS-98765
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-98765 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Summary

• Replaces react-linkify (depends on vulnerable linkify-it) with linkify-react + linkifyjs
• Fixes CVE-2026-48801: quadratic algorithmic complexity in LinkifyIt#match scan loop (DoS)
• Backport of OCPBUGS-98879, CONSOLE-5133: Replace react-linkify with linkify-react to fix CVE-2026-48801 #16814 approach to this release branch

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.