CVE-2020-28268: Prototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause

Q: How do I fix CVE-2020-28268?

controlled-merge: upgrade to newer than 1.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-28268 being exploited?

CVE-2020-28268 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-28268 affect?

CVE-2020-28268 affects controlled-merge. Severity is high (CVSS 7.5). Prototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause a denial of service and may lead to remote code execution.

Q: How urgent is CVE-2020-28268?

Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2020-28268 is a high-severity flaw (CVSS 7.5) affecting controlled-merge. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Prototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause a denial of service and may lead to remote code execution.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.6% (top 11%)
CISA exploited list	No
Weakness	CWE-1321
Published	2020-11-15
Last modified	2026-06-17

Publisher (CNA): Mend · Vendor: controlled-merge project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-11-15 23:15 UTCPublished CVE record published
2026-06-17 03:10 UTCUpdated Record last modified

controlled-merge project controlled-merge UPGRADE

Affected: >= 1.0.0 and <= 1.2.0

Fixed in: newer than 1.2.0

Safe to downgrade to: a release before 1.0.0

1. Check installed version

npm ls controlled-merge

2. UPGRADE to newer than 1.2.0

npm install controlled-merge@">1.2.0"

3. If no update is available yet, DOWNGRADE to a release before 1.0.0

npm view controlled-merge versions npm install controlled-merge@"<1.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-28268?

controlled-merge: upgrade to newer than 1.2.0. Exact commands for each OS are on this page.

Is CVE-2020-28268 being exploited?

CVE-2020-28268 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-28268 affect?

CVE-2020-28268 affects controlled-merge. Severity is high (CVSS 7.5). Prototype pollution vulnerability in 'controlled-merge' versions 1.0.0 through 1.2.0 allows attacker to cause a denial of service and may lead to remote code execution.

How urgent is CVE-2020-28268?

Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs