Skip to content

chore(deps): update dependency lodash to v4.18.1 [security] - #1371

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-lodash-vulnerability
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-lodash-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Jan 22, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
lodash (source) 4.17.21 → 4.18.1 age confidence

Lodash has Prototype Pollution Vulnerability in _.unset and _.omit functions

CVE-2025-13465 / GHSA-xxjr-mmjv-4gpg

More information

Details

Impact

Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.

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

Patches

This issue is patched on 4.17.23.

Severity

  • CVSS Score: 6.9 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H/E:P

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


lodash vulnerable to Prototype Pollution via array path bypass in _.unset and _.omit

CVE-2026-2950 / GHSA-f23m-r3pf-42rh

More information

Details

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

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


lodash vulnerable to Code Injection via _.template imports key names

CVE-2026-4800 / GHSA-r5fr-rjxr-66jc

More information

Details

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

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

lodash/lodash (lodash)

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:

v4.17.23

Compare Source


Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 was generated by Mend Renovate. View the repository job log.

@codecov

codecov Bot commented Jan 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 18.35%. Comparing base (222042a) to head (7443ca2).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1371   +/-   ##
=======================================
  Coverage   18.35%   18.35%           
=======================================
  Files         454      454           
  Lines       74865    74865           
  Branches     1594     1594           
=======================================
  Hits        13743    13743           
  Misses      61122    61122           
Flag Coverage Δ
unitTests 18.35% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions

github-actions Bot commented Jan 22, 2026 •

Copy link
Copy Markdown

Playwright test results

failed  2 failed
skipped  4 skipped

Details

stats  6 tests across 5 suites
duration  18 minutes, 7 seconds
commit  940f74d

Failed tests

chromium-setup › auth.setup.ts › authenticate as user - ( @primary @slow @read @development @staging @production )
chromium-setup › auth.setup.ts › authenticate as admin - ( @primary @slow @read @development @staging @production )

Skipped tests

chromium › pages/phone.test.ts › PhonePage › should have visible data-testids - ( @primary @slow @read @development @staging @production )
chromium › pages/training.test.ts › Training › should have visible data-testids - ( @primary @slow @read @development @staging @production )
chromium › pages/user-profile.test.ts › UserProfile › should have visible data-testids - ( @primary @slow @read @development @staging @production )
chromium › pages/work.test.ts › WorkPage › should have visible data-testids - ( @primary @slow @read @development @staging @production )

@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch from 7443ca2 to ef21cee Compare February 2, 2026 21:29
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 7 times, most recently from 53da7ad to e44e507 Compare February 10, 2026 00:24
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch from e44e507 to d31838c Compare February 17, 2026 15:50
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch from d31838c to d077b4f Compare March 5, 2026 20:38
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch from d077b4f to 7f37797 Compare March 13, 2026 10:57
@renovate renovate Bot changed the title chore(deps): update dependency lodash to v4.17.23 [security] chore(deps): update dependency lodash to v4.17.23 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-lodash-vulnerability branch March 27, 2026 01:29
@renovate renovate Bot changed the title chore(deps): update dependency lodash to v4.17.23 [security] - autoclosed chore(deps): update dependency lodash to v4.17.23 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 2 times, most recently from 7f37797 to b68d84f Compare March 30, 2026 18:12
@renovate renovate Bot changed the title chore(deps): update dependency lodash to v4.17.23 [security] chore(deps): update dependency lodash to v4.17.23 [security] - autoclosed Mar 31, 2026
@renovate renovate Bot closed this Mar 31, 2026
@renovate renovate Bot changed the title chore(deps): update dependency lodash to v4.17.23 [security] - autoclosed chore(deps): update dependency lodash to v4.17.23 [security] Apr 1, 2026
@renovate renovate Bot reopened this Apr 1, 2026
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 2 times, most recently from b68d84f to 82bf3bc Compare April 1, 2026 19:48
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch from 82bf3bc to 7904141 Compare April 8, 2026 20:49
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 3 times, most recently from 3f4187d to 115ab5d Compare April 20, 2026 18:02
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 7 times, most recently from 937cc7a to 01fc196 Compare May 4, 2026 19:47
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 9 times, most recently from fd8d6bd to 85716de Compare May 12, 2026 11:10
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 3 times, most recently from e6e0dfa to 70aa9c9 Compare May 15, 2026 17:36
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 2 times, most recently from 352ca55 to 8cb8009 Compare June 1, 2026 21:47
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch from 8cb8009 to 6df113c Compare June 13, 2026 15:53
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch from 6df113c to c54b967 Compare July 12, 2026 12:04
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch from c54b967 to 0120dda Compare July 20, 2026 20:59
@renovate
renovate Bot force-pushed the renovate/npm-lodash-vulnerability branch 4 times, most recently from 424f458 to 75000aa Compare August 6, 2026 14:07

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants