Merge Project's vulnerability footprint is concentrated in its Merge application, a JavaScript utility library with a niche but prominent deployment role in web development environments. The recurring vulnerability signal centers on prototype pollution, improper input validation, and resource-consumption issues that arise from the library's object-merging functionality and its exposure to untrusted input chains. Current severity, exploitation activity, and detailed exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Merge Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2021-3645CRITICAL merge is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') | Sep 10, 2021 | 9.8 | 31 | NO | NO |
CVE-2021-23397CRITICAL All versions of package @ianwalter/merge are vulnerable to Prototype Pollution via the main (merge) function. Maintainer suggests using @generates/merger instead. | Jul 25, 2022 | 9.8 | 30 | NO | NO |
CVE-2020-28499CRITICAL All versions of package merge are vulnerable to Prototype Pollution via _recursiveMerge . | Feb 18, 2021 | 9.8 | 29 | NO | NO |
CVE-2018-16469HIGH The merge.recursive function in the merge package <1.2.1 can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects | Oct 30, 2018 | 7.5 | 24 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Merge Project.
Media articles that mention a CVE ID that affects a product developed by Merge Project — matched by CVE ID, not by vendor name.