How severe is CVE-2021-23337?

CVE-2021-23337 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-23337?

CVE-2021-23337 affects the following packages: lodash (npm), lodash-es (npm), lodash.template (npm), lodash-template (npm), lodash-rails (RubyGems). Ecosystems affected: npm, RubyGems.

How do I fix CVE-2021-23337?

Update lodash to 4.17.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23337 is resolved across your whole dependency graph.

How do I detect CVE-2021-23337 in my npm, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lodash, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-23337 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2021-23337 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2021-23337, including 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-23337?

CVE-2021-23337 has an EPSS (Exploit Prediction Scoring System) score of 21.3%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2021-23337?

CVE-2021-23337 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2021-23337?

A Nuclei detection template exists for CVE-2021-23337, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2021-23337 published, and has it been updated?

CVE-2021-23337 was published on February 15, 2021 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm💎 RubyGems

Not in CISA KEV

HIGH severity

CVE-2021-23337 — lodash

HIGHFix: lodash/lodash@3469357

CVE-2021-23337 is a high-severity (CVSS 7.2) Code Injection vulnerability in lodash. 6 public exploit references exist, so weaponization risk is real. A fix is available for lodash — see the affected versions and patch details below.

Command Injection in lodash

Also known asGHSA-35jh-r3h4-6jhm

Published

Feb 15, 2021

Updated

Oct 20, 2026

Affected

5 pkgs

Patched

3 / 5

Exploits

6 known

Exploitation data as of Oct 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2021-23337.

EPSS Exploitation Probability

via FIRST.org ↗

21.3%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-23337 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

5 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

198Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

lodashnpm

94.5Mdownloads / week

lodash-esnpm

29.8Mdownloads / week

lodash.templatenpm

2.5Mdownloads / week

Description

Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.

Affected Packages

5 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`lodash`	all versions	4.17.21`npm install lodash@4.17.21`
📦npm	`lodash-es`	all versions	4.17.21`npm install lodash-es@4.17.21`
📦npm	`lodash.template`	all versions	No fix
📦npm	`lodash-template`	all versions	No fix
💎RubyGems	`lodash-rails`	all versions	4.17.21`bundle update lodash-rails --conservative`

Affected Products

23 products · 48 configurations

Application

lodashlodash

< 4.17.21

range

Application

active iq unified managernetapp

all

Application

cloud managernetapp

all

Application

system managernetapp

1 version

9.0

Application

banking corporate lending process managementoracle

3 versions

14.2.014.3.014.5.0

Application

banking credit facilities process managementoracle

3 versions

14.2.014.3.014.5.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.