Widely used lodash/template vulnerability enabling code execution across web apps; patch available.
CVE-2026-4800
High-severity code execution via lodash.template with untrusted imports keys.
Is CVE-2026-4800 being exploited?
Not confirmed. CVE-2026-4800 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.8% probability of exploitation in the next 30 days.
How severe is CVE-2026-4800?
CVE-2026-4800 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-4800?
Yes. A fix has been recorded for CVE-2026-4800. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-4800 affect?
CVE-2026-4800 affects Lodash lodash.template (<4.18.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4800?
Upgrade to 4.18.0+; avoid untrusted options.imports keys.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Code execution during template compilation when untrusted options.imports keys are provided; potential prototype pollution via property enumeration.
Patch when possible
- affected>= 4.0.0 and < 4.18.0
- affected>= 4.0.0 and < 4.18.0
- affected>= 4.0.0 and < 4.18.0
- affected>= 4.0.0 and < 4.18.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.