Skip to content

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

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

chore(deps): update dependency lodash to v4.18.1 [security]#688
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-lodash-vulnerability

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Oct 25, 2023

This PR contains the following updates:

Package Change Age Confidence
lodash (source) 4.17.154.18.1 age confidence

GitHub Vulnerability Alerts

CVE-2021-23337

lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.

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

CVE-2019-10744

Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.

Recommendation

Update to version 4.17.12 or later.

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

CVE-2020-8203

Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions pick, set, setWith, update, updateWith, and zipObjectDeep allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.

This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.

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

CVE-2025-13465

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

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

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

Release Notes

lodash/lodash (lodash)

v4.18.1

Compare Source

v4.18.0

Compare Source

v4.17.23

Compare Source

v4.17.21

Compare Source

v4.17.20

Compare Source

v4.17.19

v4.17.16

Compare Source


Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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.

@renovate
Copy link
Copy Markdown
Author

renovate bot commented Oct 25, 2023

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 68a3bc0 to acbc526 Compare December 3, 2023 13:19
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from acbc526 to 2a5ec85 Compare August 6, 2024 10:45
@renovate renovate bot changed the title fix(deps): update dependency lodash to v4.17.19 [security] fix(deps): update dependency lodash to v4.17.21 [security] Aug 6, 2024
@renovate renovate bot changed the title fix(deps): update dependency lodash to v4.17.21 [security] chore(deps): update dependency lodash to v4.17.21 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 2a5ec85 to a3881e7 Compare November 10, 2025 13:50
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from a3881e7 to a83e31c Compare November 18, 2025 22:46
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from a83e31c to 51b1525 Compare January 24, 2026 10:08
@renovate renovate bot changed the title chore(deps): update dependency lodash to v4.17.21 [security] chore(deps): update dependency lodash to v4.17.23 [security] Jan 24, 2026
@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 02:00
@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 from 51b1525 to c2446df Compare March 30, 2026 21: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 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 c2446df to 3a98d0f Compare April 1, 2026 13:04
@renovate renovate bot force-pushed the renovate/npm-lodash-vulnerability branch from 3a98d0f to 7532b28 Compare April 9, 2026 18:33
@renovate renovate bot changed the title chore(deps): update dependency lodash to v4.17.23 [security] chore(deps): update dependency lodash to v4.18.1 [security] Apr 9, 2026
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