chore(deps): bump lodash from 4.17.21 to 4.18.1 in /packages/personalization-utils

[dependabot]

Bumps lodash from 4.17.21 to 4.18.1.

Release notes

Sourced from lodash's releases.

4.18.1

Bugs

Fixes a ReferenceError issue in lodash lodash-es lodash-amd and lodash.template when using the template and fromPairs functions from the modular builds. See lodash/lodash#6167

These defects were related to how lodash distributions are built from the main branch using https://github.com/lodash-archive/lodash-cli. When internal dependencies change inside lodash functions, equivalent updates need to be made to a mapping in the lodash-cli. (hey, it was ahead of its time once upon a time!). We know this, but we missed it in the last release. It's the kind of thing that passes in CI, but fails bc the build is not the same thing you tested.

There is no diff on main for this, but you can see the diffs for each of the npm packages on their respective branches:

• lodash: lodash/lodash@4.18.0-npm...4.18.1-npm
• lodash-es: lodash/lodash@4.18.0-es...4.18.1-es
• lodash-amd: lodash/lodash@4.18.0-amd...4.18.1-amd
• lodash.templatelodash/lodash@4.18.0-npm-packages...4.18.1-npm-packages

4.18.0

v4.18.0

Full Changelog: lodash/lodash@4.17.23...4.18.0

Security

_.unset / _.omit: Fixed prototype pollution via constructor/prototype path traversal (GHSA-f23m-r3pf-42rh, fe8d32e). Previously, array-wrapped path segments and primitive roots could bypass the existing guards, allowing deletion of properties from built-in prototypes. Now constructor and prototype are blocked unconditionally as non-terminal path keys, matching baseSet. Calls that previously returned true and deleted the property now return false and leave the target untouched.

_.template: Fixed code injection via imports keys (GHSA-r5fr-rjxr-66jc, CVE-2026-4800, 879aaa9). Fixes an incomplete patch for CVE-2021-23337. The variable option was validated against reForbiddenIdentifierChars but importsKeys was left unguarded, allowing code injection via the same Function() constructor sink. imports keys containing forbidden identifier characters now throw "Invalid imports option passed into _.template".

Docs

• Add security notice for _.template in threat model and API docs (#6099)
• Document lower > upper behavior in _.random (#6115)
• Fix quotes in _.compact jsdoc (#6090)

lodash.* modular packages

Diff

We have also regenerated and published a select number of the lodash.* modular packages.

These modular packages had fallen out of sync significantly from the minor/patch updates to lodash. Specifically, we have brought the following packages up to parity w/ the latest lodash release because they have had CVEs on them in the past:

• lodash.orderby
• lodash.tonumber
• lodash.trim
• lodash.trimend
• lodash.sortedindexby
• lodash.zipobjectdeep
• lodash.unset
• lodash.omit
• lodash.template

Commits

• cb0b9b9 release(patch): bump main to 4.18.1 (#6177)
• 75535f5 chore: prune stale advisory refs (#6170)
• 62e91bc docs: remove n_ Node.js < 6 REPL note from README (#6165)
• 59be2de release(minor): bump to 4.18.0 (#6161)
• af63457 fix: broken tests for _.template 879aaa9
• 1073a76 fix: linting issues
• 879aaa9 fix: validate imports keys in _.template
• fe8d32e fix: block prototype pollution in baseUnset via constructor/prototype traversal
• 18ba0a3 refactor(fromPairs): use baseAssignValue for consistent assignment (#6153)
• b819080 ci: add dist sync validation workflow (#6137)
• Additional commits viewable in compare view

---

Note

Low Risk
Lockfile-only changes: bumps lodash to 4.18.1 (dev dependency in this package) and records next >=14 as an optional peer dependency, with no runtime code changes.

Overview
Updates packages/personalization-utils/package-lock.json to bump lodash from 4.17.21 to 4.18.1.

Also adds next (optional) as a peer dependency (>=14) in the lockfile metadata to match the package’s declared peer requirements.

^{Reviewed by Cursor Bugbot for commit 1474f53. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: d45719e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 1474f53

Command	Status	Duration	Result
nx test @e2e/react-sdk-next-pages	✅ Succeeded	3m 58s	View ↗
nx test @e2e/nextjs-sdk-next-app	✅ Succeeded	7m 8s	View ↗
nx test @e2e/angular-17-ssr	✅ Succeeded	5m 6s	View ↗
nx test @e2e/sveltekit	✅ Succeeded	4m 19s	View ↗
nx test @e2e/react-sdk-next-14-app	✅ Succeeded	5m 7s	View ↗
nx test @e2e/hydrogen	✅ Succeeded	4m 50s	View ↗
nx test @e2e/remix	✅ Succeeded	4m 33s	View ↗
nx test @e2e/angular-17	✅ Succeeded	6m 24s	View ↗
Additional runs (38)	✅ Succeeded	...	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-04-21 14:35:32 UTC

[nx-cloud]

View your CI Pipeline Execution ↗ for commit d45719e

Command	Status	Duration	Result
nx test @snippet/angular-17-ssr	✅ Succeeded	1m 11s	View ↗
nx test @e2e/gen1-react	✅ Succeeded	4m 46s	View ↗
nx test @snippet/remix	✅ Succeeded	57s	View ↗
nx test @snippet/react	✅ Succeeded	1m 9s	View ↗
nx test @snippet/nuxt	✅ Succeeded	55s	View ↗
nx test @snippet/gen1-next14-pages	✅ Succeeded	56s	View ↗
nx test @snippet/nextjs-sdk-next-app	✅ Succeeded	58s	View ↗
nx test @builder.io/react -- packages/react/src	✅ Succeeded	12s	View ↗
Additional runs (6)	✅ Succeeded	...	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-04-02 16:56:44 UTC