[Snyk] Upgrade lodash from 4.17.21 to 4.18.1

[tjotala]

Snyk has created this PR to upgrade lodash from 4.17.21 to 4.18.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 3 versions ahead of your current version.

• The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Predictable Value Range from Previous Values SNYK-JS-FORMDATA-10841150	250	Proof of Concept
	Arbitrary Code Injection SNYK-JS-LODASH-15869625	250	No Known Exploit
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	250	Proof of Concept
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	250	Proof of Concept
	Prototype Pollution SNYK-JS-LODASH-15053838	250	No Known Exploit
	Prototype Pollution SNYK-JS-LODASH-15869619	250	No Known Exploit

Release notes

Package name: lodash

• 4.18.1 - 2026-04-01
  

  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 #6167 (comment)

  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: 4.18.0-npm...4.18.1-npm
  • lodash-es: 4.18.0-es...4.18.1-es
  • lodash-amd: 4.18.0-amd...4.18.1-amd
  • lodash.template4.18.0-npm-packages...4.18.1-npm-packages
• 4.18.0 - 2026-03-31
  

  v4.18.0

  Full Changelog: 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
• 4.17.23 - 2026-01-21
• 4.17.21 - 2021-02-20

from lodash GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs