build(deps): bump lodash from 4.17.23 to 4.18.1

[dependabot]

Bumps lodash from 4.17.23 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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[augmentcode]

🤖 Augment PR Summary

Summary: Updates the project’s Lodash dependency to a newer 4.x release.

Changes:

• Bumped lodash from ^4.17.23 to ^4.18.1 in package.json

Technical Notes: This upgrade includes upstream security and bug-fix changes (notably around prototype pollution paths and _.template input validation), so downstream behavior may change if those APIs are used.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

[greptile-apps]

Greptile Summary

Bumps lodash from 4.17.23 to 4.18.1, picking up two security fixes: prototype pollution in _.unset/_.omit (GHSA-f23m-r3pf-42rh) and code injection in _.template via imports keys (CVE-2026-4800). Both package.json and yarn.lock are correctly updated, satisfying the automated-PR dependency-update policy.

Confidence Score: 5/5

Safe to merge — this is a targeted security patch bump with no breaking API changes.

Both package.json and yarn.lock are correctly updated. The two remaining comments are cosmetic P2 suggestions about @types/lodash version alignment and awareness of dual lodash versions for indirect deps. Neither blocks correctness or security for the project's own code.

No files require special attention.

Important Files Changed

Filename	Overview
package.json	lodash bumped from ^4.17.23 to ^4.18.1 to pick up security fixes; @types/lodash devDependency not explicitly updated
yarn.lock	Lock file now resolves two lodash versions: 4.18.1 for ^4.x ranges and 4.17.23 for ~4.17.0 pinned indirect deps; those indirect deps won't receive the security patches

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[package.json
lodash: ^4.18.1] --> B[yarn resolves
lodash 4.18.1]
    C[Indirect deps
lodash: ~4.17.0] --> D[yarn resolves
lodash 4.17.23]
    B --> E[✅ Security fixes included
GHSA-f23m-r3pf-42rh
CVE-2026-4800]
    D --> F[⚠️ Security fixes NOT included
Prototype pollution & code injection
still present in this copy]

Loading

Comments Outside Diff (1)

1. package.json, line 133 (link)

   @types/lodash version not updated

   @types/lodash is still listed as ^4.17.23. While the caret range will resolve forward, bumping it explicitly to ^4.18.1 keeps the type definitions in sync with the runtime package and makes the intent clearer.

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

_{Reviews (1): Last reviewed commit: "build(deps): bump lodash from 4.17.23 to..." | Re-trigger Greptile}

[greptile-apps]

Dual lodash versions after upgrade

The lockfile now resolves two separate lodash versions: 4.18.1 for the project's direct ^4.18.1 range, and 4.17.23 for any indirect dependency that pins to ~4.17.0. Those older transitive dependencies won't receive the prototype-pollution or code-injection fixes shipped in 4.18.0.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}