Skip to content

chore(deps): update dependency lodash@>= 4.0.0 <4.17.23 to ^4.18.1 [security]#1126

Open
loopingz wants to merge 1 commit intomainfrom
renovate/npm-lodash-=-4.0.0-4.17.23-vulnerability
Open

chore(deps): update dependency lodash@>= 4.0.0 <4.17.23 to ^4.18.1 [security]#1126
loopingz wants to merge 1 commit intomainfrom
renovate/npm-lodash-=-4.0.0-4.17.23-vulnerability

Conversation

@loopingz
Copy link
Copy Markdown
Contributor

@loopingz loopingz commented Apr 2, 2026

This PR contains the following updates:

Package Type Update Change
lodash@>= 4.0.0 <4.17.23 (source) pnpm.overrides minor [^4.17.23^4.18.1](https://renovatebot.com/diffs/npm/lodash@>= 4.0.0 <4.17.23/4.17.23/4.18.1)

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

GitHub Vulnerability Alerts

CVE-2026-2950

Impact

Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the _.unset and _.omit functions. The fix for CVE-2025-13465 only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such as Object.prototype, Number.prototype, and String.prototype.

The issue permits deletion of prototype properties but does not allow overwriting their original behavior.

Patches

This issue is patched in 4.18.0.

Workarounds

None. Upgrade to the patched version.

Severity
  • CVSS Score: 6.5 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

CVE-2026-4800

Impact

The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validation to options.imports key names. Both paths flow into the same Function() constructor sink.

When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time.

Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in. If Object.prototype has been polluted by any other vector, the polluted keys are copied into the imports object and passed to Function().

Patches

Users should upgrade to version 4.18.0.

The fix applies two changes:

  1. Validate importsKeys against the existing reForbiddenIdentifierChars regex (same check already used for the variable option)
  2. Replace assignInWith with assignWith when merging imports, so only own properties are enumerated

Workarounds

Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.

Severity
  • CVSS Score: 8.1 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Release Notes

lodash/lodash (lodash@>= 4.0.0 <4.17.23)

v4.18.1

Compare Source

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:

v4.18.0

Compare Source

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:


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@loopingz
Copy link
Copy Markdown
Contributor Author

loopingz commented Apr 2, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 24 workspace projects
 ERR_PNPM_INVALID_MINIMUM_RELEASE_AGE_EXCLUDE  Invalid value in minimumReleaseAgeExclude: Invalid versions union. Found: "lodash@>= 4.0.0 <4.17.23@4.18.1". Use exact versions only.

@loopingz loopingz requested a review from a team as a code owner April 2, 2026 13:05
@loopingz loopingz force-pushed the renovate/npm-lodash-=-4.0.0-4.17.23-vulnerability branch 12 times, most recently from 3b472bd to 7f3fa04 Compare April 8, 2026 12:36
@loopingz loopingz changed the title chore(deps): update dependency lodash@>= 4.0.0 <4.17.23 to ^4.18.1 [security] Update dependency lodash@>= 4.0.0 <4.17.23 to ^4.18.1 [SECURITY] Apr 8, 2026
@loopingz loopingz force-pushed the renovate/npm-lodash-=-4.0.0-4.17.23-vulnerability branch 8 times, most recently from e77a59f to 7f04658 Compare April 11, 2026 00:34
@loopingz loopingz changed the title Update dependency lodash@>= 4.0.0 <4.17.23 to ^4.18.1 [SECURITY] chore(deps): update dependency lodash@>= 4.0.0 <4.17.23 to ^4.18.1 [security] Apr 11, 2026
@loopingz loopingz force-pushed the renovate/npm-lodash-=-4.0.0-4.17.23-vulnerability branch 5 times, most recently from 2ce1973 to 0565b42 Compare April 17, 2026 00:46
@loopingz loopingz force-pushed the renovate/npm-lodash-=-4.0.0-4.17.23-vulnerability branch from 0565b42 to 4d75390 Compare April 17, 2026 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants