Bump lodash, grunt-legacy-log and grunt-legacy-util

[dependabot]

Bumps lodash, grunt-legacy-log and grunt-legacy-util. These dependencies needed to be updated together.
Updates 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

Updates grunt-legacy-log from 3.0.0 to 3.0.1

Changelog

Sourced from grunt-legacy-log's changelog.

• v3.0.1:
  • date: 2026-04-07
  • changes:
    • Update lodash to fix security warning (#35)
    • Update to latest grunt-legacy-log-utils
• v3.0.0:
  • date: 2020-07-27
  • changes:
    • Update dependencies
• v2.0.0:
  • date: 2018-05-19
  • changes:
    • Fix to security warnings
    • Update to latest grunt-legacy-log-utils
• v1.0.1:
  • date: 2018-03-01
  • changes:
    • Update lodash to fix security warning
• v1.0.0:
  • date: 2016-04-03
  • changes:
    • Add appveyor testing
    • Fix node.js version support
    • Peer dependency updates

Commits

• 08fd807 Release v3.0.1 (#37)
• a9fbc10 Update lodash to 4.18 and relax with caret range
• 5ac1bbb Replace unmaintained jshint/nodeunit with QUnit and ESLint
• 83ba5ad Build: update to GitHub Actions v5 to fix warnings, add Node.js 20
• bb9c280 Update badges and version number
• See full diff in compare view

Maintainer changes

This version was pushed to npm by krinkle, a new releaser for grunt-legacy-log since your current version.

Updates grunt-legacy-util from 2.0.1 to 2.0.2

Changelog

Sourced from grunt-legacy-util's changelog.

• v2.0.2:

  • date: 2026-04-07
  • changes:
    • Update "lodash" to fix security warning (#35)
    • Avoid util.isError to fix Node.js 24 support
    • Replace "exit" with "exit-x" to fix license metadata

• v2.0.1:

  • date: 2021-04-22
  • changes:
    • Update dependencies
    • Fix security warnings

• v2.0.0:

  • date: 2020-08-18
  • changes:
    • Update dependencies
    • Fix Buffer warnings by switching to Buffer.from()
    • Avoid detecting AsyncFunction as a generic object

• v1.1.1:

  • date: 2018-05-21
  • changes:
    • Fixes lodash versioning

• v1.1.0:

  • date: 2018-05-19
  • changes:
    • Security fixes

• v1.0.0:

  • date: 2016-04-03
  • changes:
    • test fixes for Windows
    • update to use the svg badge

Commits

• 4993109 Release v2.0.2 (#48)
• 7e039ad Replace "exit" with "exit-x" to fix license metadata
• 9f9a010 Add SECURITY.md
• 3c1976f Update lodash to 4.18 to fix security warning and relax with caret range
• f1c5daa Build: Add Node.js 24
• ee4e856 Avoid unsupported util.isError function removed in Node.js 24
• d33b40a Add Node.js 20 and fix Windows failure
• 268931b Build: update to GitHub Actions v5 to fix warnings
• See full diff in compare view

Maintainer changes

This version was pushed to npm by krinkle, a new releaser for grunt-legacy-util since your current version.

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.