CVE-2026-4800
Last modified
CVE-2026-4800 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) 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. EPSS estimates a 1.03% chance of exploitation in the next 30 days.
Description
Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) 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. Workarounds: Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Lodash | Lodash | >= 4.0.0, < 4.18.0 |
| Lodash | Lodash-Amd | >= 4.0.0, < 4.18.0 |
| Lodash | Lodash-Es | >= 4.0.0, < 4.18.0 |
| Lodash | Lodash.Template | >= 4.0.0, < 4.18.0 |
References
- https://cna.openjsf.org/security-advisories.htmlThird Party Advisory
- https://github.com/advisories/GHSA-35jh-r3h4-6jhmNot Applicable
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-4800?
How severe is CVE-2026-4800?
How do I fix CVE-2026-4800?
Are you affected by CVE-2026-4800?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
