chore(deps): update lodash to version 4.17.23 across all packages to fix prototype pollution issue#6037
Open
andleebsyed wants to merge 3 commits into
Conversation
🦋 Changeset detectedLatest commit: b52e9fd The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR bumps lodash from 4.17.21 to 4.17.23 in the root workspace and in packages that declare it as a devDependency (slate, slate-dom, slate-history, slate-react).
Why
4.17.23 includes a security fix for prototype pollution in _.unset and _.omit, tracked as CVE-2025-13465 (GitHub advisory). It can also be seen in Snyk Vulnerability Database. Upgrade to 4.17.23 is needed to fix this.
Lodash’s own changelog documents this release:
lodash wiki — v4.17.23 — notes the _.unset / _.omit fix and links the advisory above.
Checks
yarn test.yarn lint. (Fix errors withyarn fix.)yarn start.)yarn changeset add.)