How severe is CVE-2020-28499?

CVE-2020-28499 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.

Is CVE-2020-28499 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-28499?

CVE-2020-28499 affects Merge Project Merge. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-28499?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-28499 published?

CVE-2020-28499 was published on 2021-02-18 and last updated on 2026-06-17.

CVE-2020-28499

CVE-2020-28499 is a high-severity vulnerability in Merge Project Merge with a CVSS 3.x base score of 7.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.3)
CVSS v2: 7.5
EPSS exploit prediction: 1% (70th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Merge Project Merge
Published: 2021-02-18
Last modified: 2026-06-17

Description

All versions of package merge are vulnerable to Prototype Pollution via _recursiveMerge .

Frequently asked questions

What is CVE-2020-28499?: All versions of package merge are vulnerable to Prototype Pollution via _recursiveMerge .
How severe is CVE-2020-28499?: CVE-2020-28499 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2020-28499 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-28499?: CVE-2020-28499 affects Merge Project Merge. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-28499?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-28499 published?: CVE-2020-28499 was published on 2021-02-18 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:merge_project:merge:*:*:*:*:*:node.js:*:*

More vulnerabilities in Merge Project Merge

CVE-2021-3645 — Critical (CVSS 9.8): merge is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
CVE-2018-16469 — High (CVSS 7.5): The merge.recursive function in the merge package <1.2.1 can be tricked into adding or modifying properties of the…
CVE-2021-23397 — Medium (CVSS 5.6): All versions of package @ianwalter/merge are vulnerable to Prototype Pollution via the main (merge) function.…

All CVEs affecting Merge Project Merge →