OCPBUGS-74461: CVE-2025-13465 openshift4/ose-monitoring-plugin-rhel9: prototype pollution in _.unset and _.omit functions [openshift-4.18]

[tonyxrmdavidson]

OCPBUGS-74461: lodash bump: fix for CVE-2025-13465

Bump lodash and lodash-es to >=4.17.23 to fix prototype pollution
vulnerability in _.unset and _.omit (CVE-2025-13465, CVSS 6.9).

CVE-2025-13465 allows crafted paths like __proto__.toString to
delete methods from global prototypes via lodash's _.unset and
_.omit functions, leading to application crashes (DoS) or
security bypasses. Affected versions: 4.0.0 through 4.17.22.

Changes:

• Updated lodash-es direct dependency from ^4.17.21 to ^4.17.23
• Added lodash ^4.17.23 override for transitive copies
• Both resolve to 4.18.1 in the lockfile

Context:

• release-4.16 and release-4.17 were already fixed via later
  yarn-to-npm migrations (March 2026) which resolved lodash to
  post-fix versions
• release-4.19 was fixed by a broad dependency refresh (271dfb3,
  Feb 2026) that incidentally pulled in 4.17.23
• release-4.18 was the only branch still vulnerable because its
  yarn-to-npm migration occurred in September 2024, before lodash
  4.17.23 was published, and no subsequent npm install refreshed
  the transitive resolution

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

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-74461, 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-74461 to depend on a bug targeting a version in 4.19.0, 4.19.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:

OCPBUGS-74461: lodash bump: fix for CVE-2025-13465

Bump lodash and lodash-es to >=4.17.23 to fix prototype pollution
vulnerability in _.unset and _.omit (CVE-2025-13465, CVSS 6.9).

CVE-2025-13465 allows crafted paths like __proto__.toString to
delete methods from global prototypes via lodash's _.unset and
_.omit functions, leading to application crashes (DoS) or
security bypasses. Affected versions: 4.0.0 through 4.17.22.

Changes:

• Updated lodash-es direct dependency from ^4.17.21 to ^4.17.23
• Added lodash ^4.17.23 override for transitive copies
• Both resolve to 4.18.1 in the lockfile

Context:

• release-4.16 and release-4.17 were already fixed via later
  yarn-to-npm migrations (March 2026) which resolved lodash to
  post-fix versions
• release-4.19 was fixed by a broad dependency refresh (271dfb3,
  Feb 2026) that incidentally pulled in 4.17.23
• release-4.18 was the only branch still vulnerable because its
  yarn-to-npm migration occurred in September 2024, before lodash
  4.17.23 was published, and no subsequent npm install refreshed
  the transitive resolution

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: cb77f9b0-d098-44c9-87dd-489d6a2635d3

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

[tonyxrmdavidson]

/jira refresh

[openshift-ci-robot]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-74461, 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-74461 to depend on a bug targeting a version in 4.19.0, 4.19.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:

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

[tonyxrmdavidson]

/jira refresh

[openshift-ci-robot]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-74461, 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-74461 to depend on a bug targeting a version in 4.19.0, 4.19.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:

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

[tonyxrmdavidson]

/jira refresh

[openshift-ci-robot]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-74461, 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.

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:

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

[tonyxrmdavidson]

/jira refresh

[openshift-ci-robot]

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-74461, 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.18.z) matches configured target version for branch (4.18.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-74467 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-74467 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (juzhao@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.

[tonyxrmdavidson]

/pipeline required

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws-ovn-upgrade
/test e2e-hypershift-conformance

[germanparente]

/lgtm
/label approved
/label qe-approved

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws-ovn-upgrade
/test e2e-hypershift-conformance

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@tonyxrmdavidson: This pull request references Jira Issue OCPBUGS-74461, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-74467 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-74467 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (juzhao@redhat.com), skipping review request.

Details

In response to this:

OCPBUGS-74461: lodash bump: fix for CVE-2025-13465

Bump lodash and lodash-es to >=4.17.23 to fix prototype pollution
vulnerability in _.unset and _.omit (CVE-2025-13465, CVSS 6.9).

CVE-2025-13465 allows crafted paths like __proto__.toString to
delete methods from global prototypes via lodash's _.unset and
_.omit functions, leading to application crashes (DoS) or
security bypasses. Affected versions: 4.0.0 through 4.17.22.

Changes:

• Updated lodash-es direct dependency from ^4.17.21 to ^4.17.23
• Added lodash ^4.17.23 override for transitive copies
• Both resolve to 4.18.1 in the lockfile

Context:

• release-4.16 and release-4.17 were already fixed via later
  yarn-to-npm migrations (March 2026) which resolved lodash to
  post-fix versions
• release-4.19 was fixed by a broad dependency refresh (271dfb3,
  Feb 2026) that incidentally pulled in 4.17.23
• release-4.18 was the only branch still vulnerable because its
  yarn-to-npm migration occurred in September 2024, before lodash
  4.17.23 was published, and no subsequent npm install refreshed
  the transitive resolution

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]

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

@tonyxrmdavidson: Jira Issue OCPBUGS-74461: All pull requests linked via external trackers have merged:

• openshift/monitoring-plugin#1141
• openshift/monitoring-plugin#1141

Jira Issue OCPBUGS-74461 has been moved to the MODIFIED state.

Details

In response to this:

OCPBUGS-74461: lodash bump: fix for CVE-2025-13465

Bump lodash and lodash-es to >=4.17.23 to fix prototype pollution
vulnerability in _.unset and _.omit (CVE-2025-13465, CVSS 6.9).

CVE-2025-13465 allows crafted paths like __proto__.toString to
delete methods from global prototypes via lodash's _.unset and
_.omit functions, leading to application crashes (DoS) or
security bypasses. Affected versions: 4.0.0 through 4.17.22.

Changes:

• Updated lodash-es direct dependency from ^4.17.21 to ^4.17.23
• Added lodash ^4.17.23 override for transitive copies
• Both resolve to 4.18.1 in the lockfile

Context:

• release-4.16 and release-4.17 were already fixed via later
  yarn-to-npm migrations (March 2026) which resolved lodash to
  post-fix versions
• release-4.19 was fixed by a broad dependency refresh (271dfb3,
  Feb 2026) that incidentally pulled in 4.17.23
• release-4.18 was the only branch still vulnerable because its
  yarn-to-npm migration occurred in September 2024, before lodash
  4.17.23 was published, and no subsequent npm install refreshed
  the transitive resolution

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.