How severe is CVE-2021-23450?

CVE-2021-23450 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-23450?

CVE-2021-23450 affects the following packages: dojo (npm). Ecosystems affected: npm.

How do I fix CVE-2021-23450?

No patched version of dojo has shipped for CVE-2021-23450 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2021-23450 in my npm dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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

Yes. There are 5 known exploit references for CVE-2021-23450, including 5 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-23450?

CVE-2021-23450 has an EPSS (Exploit Prediction Scoring System) score of 30.4%, 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-23450?

CVE-2021-23450 is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2021-23450 was published on December 17, 2021 and was last updated on October 10, 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

Not in CISA KEV

CRITICAL severity

CVE-2021-23450 — dojo

CRITICAL

CVE-2021-23450 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in dojo. 5 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Prototype Pollution in dojo

Also known asGHSA-m8gw-hjpr-rjv7

Published

Dec 17, 2021

Updated

Oct 10, 2026

Affected

1 pkg

Patched

See advisory

Exploits

5 known

Exploitation data as of Oct 9, 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-23450.

EPSS Exploitation Probability

via FIRST.org ↗

30.4%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-23450 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

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

Real-World Exposure

1 pkg 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.

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

dojonpm

15Kdownloads / week

Description

All versions of package dojo are vulnerable to Prototype Pollution via the setObject function.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`dojo`	all versions	No fix

Affected Products

5 products · 10 configurations

debian linuxdebian

1 version

10.0

Application

dojolinuxfoundation

< 1.17.0

range

Application

communications policy managementoracle

1 version

12.6.0.0.0

Application

primavera unifieroracle

≥ 17.7 && ≤ 17.12

4 versions

18.819.1220.1221.12

Application

weblogic serveroracle

2 versions

12.2.1.4.014.1.1.0.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.