Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

merge-change vulnerabilities and fixes

Recent CVEs affecting merge-change, with upgrade or downgrade steps. 1 tracked.

Also searched as: merge change.

merge-change has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2021-08-11. Highest priority: CVE-2021-23421 (score 46/100).

FAQ

How do I fix merge-change vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is merge-change being exploited right now?

None of the tracked merge-change CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which merge-change CVE should I patch first?

CVE-2021-23421 currently ranks highest (46/100): All versions of package merge-change are vulnerable to Prototype Pollution via the utils.set function..

← Back to latest CVEs