OCPBUGS-70285,OCPBUGS-74473,OCPBUGS-67252,OCPBUGS-66283: Fix CVEs via upgrading yarn.lock

[upalatucci]

Summary

Fix CVEs by adding yarn resolutions to force patched dependency versions.

Dependency Updates

• node-forge: 1.3.1 → 1.3.3 (CVE-2025-12816, CVE-2025-66031)
• lodash: 4.17.21 → 4.17.23 (CVE-2025-13465)
• qs: 6.10.5 / 6.13.0 → 6.14.2 (CVE-2025-15284)

Jira Issues

• OCPBUGS-70285 (CVE-2025-15284 — qs DoS)
• OCPBUGS-74473 (CVE-2025-13465 — lodash prototype pollution)
• OCPBUGS-67252 (CVE-2025-12816 — node-forge interpretation conflict)
• OCPBUGS-66283 (CVE-2025-66031 — node-forge ASN.1 recursion)

Made with Cursor

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

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
• Post copyable unit tests in a comment

---

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

[openshift-ci-robot]

@upalatucci: This pull request references Jira Issue OCPBUGS-70285, which is invalid:

• expected the vulnerability to target either version "4.21." or "openshift-4.21.", but it targets "4.22.0" instead
• 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-70285 to depend on a bug targeting a version in 4.22.0 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-74473, which is invalid:

• expected the vulnerability to target either version "4.21." or "openshift-4.21.", but it targets "4.20.z" instead
• 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-74473 to depend on a bug targeting a version in 4.22.0 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-67252, which is invalid:

• expected the vulnerability to target either version "4.21." or "openshift-4.21.", but it targets "4.20.z" instead
• 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-67252 to depend on a bug targeting a version in 4.22.0 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-66283, which is invalid:

• expected the vulnerability to target either version "4.21." or "openshift-4.21.", but it targets "4.20.z" instead
• 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-66283 to depend on a bug targeting a version in 4.22.0 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:

Summary

Fix CVEs by adding yarn resolutions to force patched dependency versions.

Dependency Updates

• node-forge: 1.3.1 → 1.3.3 (CVE-2025-12816, CVE-2025-66031)
• lodash: 4.17.21 → 4.17.23 (CVE-2025-13465)
• qs: 6.10.5 / 6.13.0 → 6.14.2 (CVE-2025-15284)

Jira Issues

• OCPBUGS-70285 (CVE-2025-15284 — qs DoS)
• OCPBUGS-74473 (CVE-2025-13465 — lodash prototype pollution)
• OCPBUGS-67252 (CVE-2025-12816 — node-forge interpretation conflict)
• OCPBUGS-66283 (CVE-2025-66031 — node-forge ASN.1 recursion)

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 [upalatucci]

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

[upalatucci]

/retest

[openshift-ci]

@upalatucci: 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/images	811bccf	link	true	/test images
ci/prow/e2e	811bccf	link	true	/test e2e

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.