Lodash
lodash vulnerable to Code Injection via `_.template` imports key names
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, and 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, so if Object.prototype has been polluted by another vector the polluted keys are copied into the imports object and passed to Function(). The issue is fixed in 4.18.1 for lodash, lodash-es, lodash-amd, and lodash.template. As a workaround, do not pass untrusted input as key names in options.imports; use only developer-controlled, static key names.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.0.0, < 4.18.1
Fixed in 4.18.1
- >= 4.0.0, < 4.18.1
Fixed in 4.18.1
- >= 4.0.0, < 4.18.1
Fixed in 4.18.1
- >= 4.0.0, < 4.18.1
Fixed in 4.18.1
Mitigation
Upgrade lodash to 4.18.1 or later.
Upgrade lodash-es to 4.18.1 or later.
Upgrade lodash-amd to 4.18.1 or later.
Upgrade lodash.template to 4.18.1 or later.
References
- Vendor advisory github.com/lodash/lodash/security/advisories/G…
Timeline
Days relative to CVE publicationFirst public PoC 6 h after publication; not in CISA KEV. First PoC: threalwinky/CVE-2026-4800-POC (created 1 Apr 2026, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs
PoCs 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| threalwinky/CVE-2026-4800-POC | 1 Apr 2026 +6 h | 3 | PoC |
| SvenLie/next-rep-CVE-2026-4800 | 7 Apr 2026 +6.8 d | 0 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.