HighGHSA-r5fr-rjxr-66jcCVE-2026-4800

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

Published 1 Apr 2026 · Updated 17 Oct 2026

Affected packages

Affected
>=4.0.0 <4.18.0
Fixed in
4.18.0
Update to the fixed version for your release line, for example:npm install lodash@4.18.0
Affected
>=4.0.0 <4.18.0
Fixed in
4.18.0
Update to the fixed version for your release line, for example:npm install lodash-es@4.18.0
Affected
>=4.0.0 <4.18.0
Fixed in
4.18.0
Update to the fixed version for your release line, for example:npm install lodash-amd@4.18.0
Affected
>=4.0.0 <4.18.0
Fixed in
4.18.0
Update to the fixed version for your release line, for example:npm install lodash.template@4.18.0

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.

Is GHSA-r5fr-rjxr-66jc in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected lodash, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.