Prototype pollution in min-dash

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2021-23460: 2.19% estimated exploitation activity in the next 30 days; percentile 82.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The set method is vulnerable to prototype pollution with specially crafted inputs. 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.

Published by the source

1 Feb 2022, 00:44 UTC

Last modified by the source

18 Jul 2025, 20:12 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2m53-83f3-562j

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2m53-83f3-562j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-23460

Advisory: Prototype pollution in min-dash
IDs: CVE-2021-23460, GHSA-2m53-83f3-562j
Record: https://patchnext.com/advisories/cve-2021-23460 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: min-dash 3.8.1; org.webjars.npm:min-dash 3.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm min-dash: affected < 3.8.1; fixed in 3.8.1
- Maven org.webjars.npm:min-dash: affected < 3.8.1; fixed in 3.8.1

## Suggested inspection (read-only)
- `npm ls min-dash --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- Maven org.webjars.npm:min-dash: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on min-dash, org.webjars.npm:min-dash.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2m53-83f3-562j (OSV record GHSA-2m53-83f3-562j lists affected ranges: npm min-dash >=0 =0 <3.8.1 (fixed))
- Verified: https://github.com/advisories/GHSA-2m53-83f3-562j (GitHub-reviewed advisory GHSA-2m53-83f3-562j lists affected ranges: npm min-dash >=0 =0 <3.8.1)

Commands are suggestions: review each one before running it.