Lodash.Template
Approved changes feed: RSS · Atom
cpe:2.3:a:lodash:lodash.template:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Lodash (116b040a-d129-527f-bca2-0cc13672da41) |
|---|---|
| Product | Lodash.Template (f19cbf97-8a67-53ff-a62d-9d89be763b19) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-4800 |
vulnerable | 2026-06-08 08:07:02.391230 |
lodash vulnerable to Code Injection via `_.template` imports key names
HIGH (8.1)
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.
Published: 2026-03-31T19:25:55.987Z
Updated: 2026-10-15T06:39:20.655Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.