Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 22, 2026

This PR contains the following updates:

Package Change Age Confidence
lodash (source) 4.17.214.17.23 age confidence

GitHub Vulnerability Alerts

CVE-2025-13465

Impact

Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.

The issue permits deletion of properties but does not allow overwriting their original behavior.

Patches

This issue is patched on 4.17.23.


Release Notes

lodash/lodash (lodash)

v4.17.23

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovatebot label Jan 22, 2026
@renovate renovate bot changed the title chore(deps): update dependency lodash to v4.17.23 [security] chore(deps): update dependency lodash to v4.17.23 [security] - autoclosed Jan 27, 2026
@renovate renovate bot closed this Jan 27, 2026
@renovate renovate bot deleted the renovate/npm-lodash-vulnerability branch January 27, 2026 09:32
@renovate renovate bot changed the title chore(deps): update dependency lodash to v4.17.23 [security] - autoclosed chore(deps): update dependency lodash to v4.17.23 [security] Jan 27, 2026
@renovate renovate bot reopened this Jan 27, 2026
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch 2 times, most recently from 3ed33db to e83226a Compare January 27, 2026 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants