Skip to content
Noroxi
NVD / CVE Program· CNA openjs

CVE-2026-4800: lodash vulnerable to Code Injection via `_.template` imports key names

Noroxi assessment

Priority: Plan (action score 40/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.8% (FIRST EPSS); higher than 86.4% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: lodash lodash 4.18.1; lodash lodash-amd 4.18.1; lodash lodash-es 4.18.1.

Add it to your regular patch cycle. Upgrade to lodash lodash 4.18.1; lodash lodash-amd 4.18.1; lodash lodash-es 4.18.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available
Published
Mar 31, 2026
Updated
Oct 15, 2026
EPSS
2.8% · 86th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.8
CNA · openjs
8.1
1.7 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-4800

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
lodashlodash
lodashlodash-amd
lodashlodash-es
lodashlodash.template

Is the Lodash on your site affected?

The free JavaScript library scanner reads the Lodash version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.

Scan JavaScript libraries

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • lodash lodash4.0.0 and later · before 4.18.0
  • lodash lodash-amd4.0.0 and later · before 4.18.0
  • lodash lodash-es4.0.0 and later · before 4.18.0
  • lodash lodash.template4.0.0 and later · before 4.18.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openjs). Independent of NVD's CPE analysis and usually ahead of it.

  • lodash lodash

    • 4.18.1not affected
    • 4.0.0 and later · before 4.18.1affected · semver
  • lodash lodash-amd

    • 4.18.1not affected
    • 4.0.0 and later · before 4.18.1affected · semver
  • lodash lodash-es

    • 4.18.1not affected
    • 4.0.0 and later · before 4.18.1affected · semver
  • lodash lodash.template

    • 4.18.1not affected
    • 4.0.0 and later · before 4.18.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10cockpit-ha-clusterbefore 0.12.1-1.el10_1.30.12.1-1.el10_1.3
AlmaLinux:9pcsbefore 0.11.11-2.el9_8.10.11.11-2.el9_8.1
AlmaLinux:9pcsbefore 0.11.10-1.el9_7.30.11.10-1.el9_7.3
AlmaLinux:9pcs-snmpbefore 0.11.11-2.el9_8.10.11.11-2.el9_8.1
AlmaLinux:9pcs-snmpbefore 0.11.10-1.el9_7.30.11.10-1.el9_7.3
Debian:12node-lodashbefore 4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u14.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1
Debian:13node-lodashbefore 4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u14.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1
Debian:14node-lodashbefore 4.18.1+dfsg-14.18.1+dfsg-1
npmlodashfrom 4.0.0 · before 4.18.04.18.0
npmlodash-amdfrom 4.0.0 · before 4.18.04.18.0
npmlodash-esfrom 4.0.0 · before 4.18.04.18.0
npmlodash.templatefrom 4.0.0 · before 4.18.04.18.0
Red Hat:ansible_automation_platform_developer:2.6::el10python3-clickbefore 0:8.3.3-1.el10ap0:8.3.3-1.el10ap
Red Hat:ansible_automation_platform_developer:2.6::el9automation-controllerbefore 0:4.7.12-1.el9ap0:4.7.12-1.el9ap
Red Hat:ansible_automation_platform_developer:2.6::el9automation-controller-clibefore 0:4.7.12-1.el9ap0:4.7.12-1.el9ap
Red Hat:ansible_automation_platform_developer:2.6::el9python3.12-clickbefore 0:8.3.3-1.el9ap0:8.3.3-1.el9ap
Red Hat:ansible_automation_platform_developer:2.6::el9python3.12-cryptographybefore 0:46.0.7-1.el9ap0:46.0.7-1.el9ap
Red Hat:ansible_automation_platform_developer:2.6::el9python3.12-cryptography-debuginfobefore 0:46.0.7-1.el9ap0:46.0.7-1.el9ap
Red Hat:ansible_automation_platform_developer:2.6::el9python3.12-cryptography-debugsourcebefore 0:46.0.7-1.el9ap0:46.0.7-1.el9ap
Red Hat:ansible_automation_platform_developer:2.6::el9receptorbefore 0:1.6.5-1.el9ap0:1.6.5-1.el9ap
Red Hat:ansible_automation_platform_developer:2.6::el9receptorctlbefore 0:1.6.5-1.el9ap0:1.6.5-1.el9ap
Red Hat:ansible_automation_platform:2.6::el10receptorbefore 0:1.6.5-1.el10ap0:1.6.5-1.el10ap
Red Hat:ansible_automation_platform:2.6::el10receptor-debuginfobefore 0:1.6.5-1.el10ap0:1.6.5-1.el10ap
Red Hat:ansible_automation_platform:2.6::el10receptor-debugsourcebefore 0:1.6.5-1.el10ap0:1.6.5-1.el10ap

+65

Other highest-scoring records for the same primary product.

  • CVE-2019-10744Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution.
    38Monitor
  • CVE-2021-23337Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
    34Monitor
  • CVE-2020-8203Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2020-28500Feb 15, 2021 · Regular Expression Denial of Service (ReDoS)
    23Monitor
  • ← EarlierCVE-2025-13465Jan 21, 2026 · Prototype Pollution Vulnerability in Lodash _.unset and _.omit functions
    28Monitor
  • ← EarlierCVE-2026-2950Mar 31, 2026 · lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
lodash lodash4.18.1Vendor (CNA)
lodash lodash-amd4.18.1Vendor (CNA)
lodash lodash-es4.18.1Vendor (CNA)
lodash lodash.template4.18.1Vendor (CNA)
almalinux:cockpit-ha-cluster0.12.1-1.el10_1.3 · AlmaLinux:10Package registry (OSV)
almalinux:pcs0.11.10-1.el9_7.3 · AlmaLinux:9Package registry (OSV)
almalinux:pcs-snmp0.11.10-1.el9_7.3 · AlmaLinux:9Package registry (OSV)
debian:node-lodash4.17.21+dfsg+~cs8.31.198.20210220-9+deb12u1 · Debian:12Package registry (OSV)
debian:node-lodash4.17.21+dfsg+~cs8.31.198.20210220-9+deb13u1 · Debian:13Package registry (OSV)
npm:lodash4.18.0Package registry (OSV)
npm:lodash-amd4.18.0Package registry (OSV)
npm:lodash-es4.18.0Package registry (OSV)
npm:lodash.template4.18.0Package registry (OSV)
red hat:cockpit0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-bridge0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-debuginfo0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-debugsource0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-doc0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-packagekit0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:cockpit-storaged0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:cockpit-system0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-ws0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:cockpit-ws-selinux0:356.1-1.el9_8 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:pcs0:0.11.10-1.el9_7.3 · Red Hat:enterprise_linux:9::highavailabilityPackage registry (OSV)
red hat:pcs-snmp0:0.11.10-1.el9_7.3 · Red Hat:enterprise_linux:9::highavailabilityPackage registry (OSV)
rocky linux:cockpit-image-builder0:94.3-1.el10_2 · Rocky Linux:10Package registry (OSV)
rocky linux:pcs0:0.11.10-1.el9_7.3 · Rocky Linux:9Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:32026-04-01
Proof-of-concept repository on GitHubstars:02026-04-07

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodayOct 30, 2026+213 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records