Thanks to visit codestin.com
Credit goes to github.com

Skip to content

chore(deps): bump lodash from 4.17.23 to 4.18.1#768

Merged
CataldoMazzilli merged 2 commits into
develfrom
chore/deps-lodash-4.18.1
Apr 16, 2026
Merged

chore(deps): bump lodash from 4.17.23 to 4.18.1#768
CataldoMazzilli merged 2 commits into
develfrom
chore/deps-lodash-4.18.1

Conversation

@CataldoMazzilli
Copy link
Copy Markdown
Member

Bump lodash from 4.17.23 to 4.18.1

Automated minor/patch update opened by the update-deps skill.

Questo aggiornamento risolve una vulnerabilità HIGH su lodash (<=4.17.23): Code Injection via _.template (GHSA-r5fr-rjxr-66jc) e Prototype Pollution via array path bypass in _.unset / _.omit (GHSA-f23m-r3pf-42rh).

Changelog

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:


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 (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:

Notes

  • Base branch: devel
  • Command: ncu -u --target minor --filter lodash && npm install
  • Only package.json and package-lock.json were modified.

🤖 Generated by the update-deps skill.

lisaparma
lisaparma previously approved these changes Apr 16, 2026
Remove the ^ range prefix to lock lodash to the exact version and
prevent unintended minor/patch drift.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@sonarqube-zextras
Copy link
Copy Markdown

@CataldoMazzilli CataldoMazzilli merged commit 0635e31 into devel Apr 16, 2026
3 checks passed
@CataldoMazzilli CataldoMazzilli deleted the chore/deps-lodash-4.18.1 branch April 16, 2026 07:53
@ZxBot
Copy link
Copy Markdown
Contributor

ZxBot commented Apr 24, 2026

🎉 This PR is included in version 14.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@ZxBot ZxBot added the released label Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants