Skip to content

OCPBUGS-81611, OCPBUGS-79454, OCPBUGS-73656: CVE remediation for lodash, immutable, qs (release-4.20)#190

Open
pcbailey wants to merge 2 commits intoopenshift:release-4.20from
pcbailey:fix/cve-new-status-release-4.20
Open

OCPBUGS-81611, OCPBUGS-79454, OCPBUGS-73656: CVE remediation for lodash, immutable, qs (release-4.20)#190
pcbailey wants to merge 2 commits intoopenshift:release-4.20from
pcbailey:fix/cve-new-status-release-4.20

Conversation

@pcbailey
Copy link
Copy Markdown

@pcbailey pcbailey commented Apr 16, 2026

Multi-branch CVE remediation for Open Jira issues in New status (lodash CVE-2026-4800 / CVE-2025-13465, immutable CVE-2026-29063, qs CVE-2025-15284, react-router CVE-2026-22029).

This PR: release-4.20 — Yarn resolutions for lodash@4.18.1 and qs@6.14.2; immutable@3.x lock entry updated to 3.8.3.

Related: main — #189

Verification: yarn install and yarn build.

Made with Cursor

- Yarn resolutions: lodash@4.18.1, qs@6.14.2
- Bump immutable@3.x lock entry to 3.8.3 (CVE-2026-29063)

Relates to New-status OCPBUGS on openshift-4.20.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 16, 2026

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: a7b93a55-fb53-4379-b732-f9a166e37b2f

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

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 and usage tips.

@openshift-ci openshift-ci Bot requested review from metalice and upalatucci April 16, 2026 01:37
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 16, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2026
@avivtur
Copy link
Copy Markdown

avivtur commented Apr 16, 2026

/retest

@openshift-merge-bot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 2091400 and 2 for PR HEAD 5721d04 in total

@pcbailey
Copy link
Copy Markdown
Author

/retest

@pcbailey pcbailey changed the title fix(deps): CVE remediation for lodash, immutable, qs (release-4.20) OCPBUGS-81611, OCPBUGS-79454: CVE remediation for lodash, immutable, qs (release-4.20) Apr 16, 2026
@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 a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 16, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@pcbailey: This pull request references Jira Issue OCPBUGS-81611, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-81611 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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-79454, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-79454 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Multi-branch CVE remediation for Open Jira issues in New status (lodash CVE-2026-4800 / CVE-2025-13465, immutable CVE-2026-29063, qs CVE-2025-15284).

This PR: release-4.20 — Yarn resolutions for lodash@4.18.1 and qs@6.14.2; immutable@3.x lock entry updated to 3.8.3.

Related: main — #189

Verification: yarn install and yarn build.

Made with Cursor

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.

- Bump react-router-dom-v5-compat to ^6.30.3
- Yarn resolution: @remix-run/router@1.23.2 (GHSA-2w69-qvjg-hvjx)
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2026
@pcbailey
Copy link
Copy Markdown
Author

Pushed an additional commit for CVE-2026-22029 (GHSA-2w69-qvjg-hvjx): bump react-router-dom-v5-compat to ^6.30.3 and pin @remix-run/router to 1.23.2 (Yarn resolutions on release branches; npm overrides on main). The v5 react-router line is not in the affected 7.x range; the fix targets the v6 compat stack bundled with the console SDK.

@openshift-ci-robot
Copy link
Copy Markdown

@pcbailey: This pull request references Jira Issue OCPBUGS-81611, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-81611 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

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

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-79454 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

Details

In response to this:

Multi-branch CVE remediation for Open Jira issues in New status (lodash CVE-2026-4800 / CVE-2025-13465, immutable CVE-2026-29063, qs CVE-2025-15284, react-router CVE-2026-22029).

This PR: release-4.20 — Yarn resolutions for lodash@4.18.1 and qs@6.14.2; immutable@3.x lock entry updated to 3.8.3.

Related: main — #189

Verification: yarn install and yarn build.

Made with Cursor

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.

@pcbailey pcbailey changed the title OCPBUGS-81611, OCPBUGS-79454: CVE remediation for lodash, immutable, qs (release-4.20) OCPBUGS-81611, OCPBUGS-79454, OCPBUGS-73656: CVE remediation for lodash, immutable, qs (release-4.20) Apr 16, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@pcbailey: This pull request references Jira Issue OCPBUGS-81611, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-81611 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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-79454, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-79454 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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-73656, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-73656 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Multi-branch CVE remediation for Open Jira issues in New status (lodash CVE-2026-4800 / CVE-2025-13465, immutable CVE-2026-29063, qs CVE-2025-15284, react-router CVE-2026-22029).

This PR: release-4.20 — Yarn resolutions for lodash@4.18.1 and qs@6.14.2; immutable@3.x lock entry updated to 3.8.3.

Related: main — #189

Verification: yarn install and yarn build.

Made with Cursor

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.

@pcbailey
Copy link
Copy Markdown
Author

/retest

2 similar comments
@pcbailey
Copy link
Copy Markdown
Author

/retest

@upalatucci
Copy link
Copy Markdown

/retest

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 23, 2026

@pcbailey: 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 openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 24, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 24, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avivtur, pcbailey, upalatucci

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:
  • OWNERS [avivtur,pcbailey,upalatucci]

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a 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 Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants