Skip to content

OCPBUGS-98765: Bump linkify-it to 5.0.2 to fix CVE-2026-48801 - #17073

Open
prabhapa wants to merge 1 commit into
openshift:release-4.19from
prabhapa:cve/release-4.19/OCPBUGS-98765
Open

OCPBUGS-98765: Bump linkify-it to 5.0.2 to fix CVE-2026-48801#17073
prabhapa wants to merge 1 commit into
openshift:release-4.19from
prabhapa:cve/release-4.19/OCPBUGS-98765

Conversation

@prabhapa

Copy link
Copy Markdown

CVE-2026-48801: linkify-it ReDoS vulnerability

Bumps the transitive dependency linkify-it from 2.1.0 to 5.0.2 via yarn resolutions to address CVE-2026-48801 (CVSS 7.5 Moderate).

Vulnerability

linkify-it < 5.0.1 has O(N²) algorithmic complexity in LinkifyIt.prototype.match, enabling ReDoS (Regular Expression Denial of Service) via crafted input with many fuzzy links or emails (CWE-1333).

Changes

  • Added "linkify-it": "^5.0.1" to frontend/package.json resolutions block to override the transitive dependency pinned by react-linkify@0.2.2
  • linkify-it: 2.1.0 → 5.0.2
  • uc.micro (child dep): 1.0.6 → 2.1.0

Validation

  • Jest unit tests: 9/9 passed
  • Webpack production build: succeeded (127s, zero linkify-related warnings)
  • Runtime compatibility verified: react-linkify@0.2.2 works correctly with linkify-it 5.x API

Jira

Bumps the transitive dependency linkify-it from 2.1.0 to 5.0.2 via yarn
resolutions to address CVE-2026-48801 (ReDoS via O(N²) complexity).
@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-moderate Referenced Jira bug's severity is moderate 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 Aug 21, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@prabhapa: 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 POST 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:

CVE-2026-48801: linkify-it ReDoS vulnerability

Bumps the transitive dependency linkify-it from 2.1.0 to 5.0.2 via yarn resolutions to address CVE-2026-48801 (CVSS 7.5 Moderate).

Vulnerability

linkify-it < 5.0.1 has O(N²) algorithmic complexity in LinkifyIt.prototype.match, enabling ReDoS (Regular Expression Denial of Service) via crafted input with many fuzzy links or emails (CWE-1333).

Changes

  • Added "linkify-it": "^5.0.1" to frontend/package.json resolutions block to override the transitive dependency pinned by react-linkify@0.2.2
  • linkify-it: 2.1.0 → 5.0.2
  • uc.micro (child dep): 1.0.6 → 2.1.0

Validation

  • Jest unit tests: 9/9 passed
  • Webpack production build: succeeded (127s, zero linkify-related warnings)
  • Runtime compatibility verified: react-linkify@0.2.2 works correctly with linkify-it 5.x API

Jira

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

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

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: 08f58d21-3f91-4623-b89d-ffc063dcce35

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

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

@openshift-ci
openshift-ci Bot requested review from Leo6Leo and cajieh August 21, 2026 14:49
@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@prabhapa

Copy link
Copy Markdown
Author

/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 Aug 21, 2026
@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

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

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-moderate Referenced Jira bug's severity is moderate 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