How severe is CVE-2021-23460?

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

Which packages are affected by CVE-2021-23460?

CVE-2021-23460 affects the following packages: org.webjars.npm:min-dash (Maven), min-dash (npm). Ecosystems affected: Maven, npm.

How do I fix CVE-2021-23460?

Update org.webjars.npm:min-dash to 3.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23460 is resolved across your whole dependency graph.

How do I detect CVE-2021-23460 in my Maven, npm dependencies?

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

How do I mitigate CVE-2021-23460 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-23460 actively exploited in the wild?

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

CVE-2021-23460 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 82th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-23460?

CVE-2021-23460 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-23460 published, and has it been updated?

CVE-2021-23460 was published on January 21, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven📦 npm

Not in CISA KEV

HIGH severity

CVE-2021-23460 — min-dash

HIGHFix: bpmn-io/min-dash#21

CVE-2021-23460 is a high-severity (CVSS 7.5) CWE-1321 vulnerability in org.webjars.npm:min-dash. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.webjars.npm:min-dash — see the affected versions and patch details below.

Prototype pollution in min-dash

Also known asGHSA-2m53-83f3-562j

Published

Jan 21, 2022

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2021-23460 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% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

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

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

min-dashnpm

736Kdownloads / week

Description

Impact

The set method is vulnerable to prototype pollution with specially crafted inputs.

// insert the following into poc.js and run node poc,js (after installing the package)
 
let parser = require("min-dash");
parser.set({}, [["__proto__"], "polluted"], "success");
console.log(polluted);

Patches

min-dash>=3.8.1 fix the issue.

Workarounds

No workarounds exist for the issue.

References

Closed via https://github.com/bpmn-io/min-dash/pull/21.

Credits

Credits to Cristian-Alexandru STAICU who found the vulnerability and to Idan Digmi from the Snyk Security Team who reported the vulnerability to us, responsibly.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.webjars.npm:min-dash`	all versions	3.8.1`org.webjars.npm:min-dash:3.8.1`
📦npm	`min-dash`	all versions	3.8.1`npm install min-dash@3.8.1`

Affected Products

1 product · 1 configurations

Application

min-dashcamunda

< 3.8.1

range

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.

The package min-dash before 3.8.1 are vulnerable to Prototype Pollution …

snyk.ioNVDJan 2022

The package min-dash before 3.8.1 are vulnerable to Prototype Pollution …

snyk.ioNVDJan 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:min-dash, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.webjars.npm:min-dash to 3.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23460 is resolved across your whole dependency graph.
Workarounds
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.

Frequently Asked Questions

### Impact The `set` method is vulnerable to prototype pollution with specially crafted inputs. ```javascript // insert the following into poc.js and run node poc,js (after installing the package) let parser = require("min-dash"); parser.set({}, [["__proto__"], "polluted"], "success"); console.log(polluted); ``` ### Patches `min-dash>=3.8.1` fix the issue. ### Workarounds No workarounds exist for the issue. ### References Closed via https://github.com/bpmn-io/min-dash/pull/21. ### Credits Credits to Cristian-Alexandru STAICU who found the vulnerability and to Idan Digmi from the Sn