CVE-2020-28267: Prototype pollution vulnerability in '@strikeentco/set' version 1.0.0 allows attacker to cause a denial of ser

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

set: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2020-28267 being exploited?

CVE-2020-28267 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-28267 affect?

CVE-2020-28267 affects set. Severity is high (CVSS 7.5). Prototype pollution vulnerability in '@strikeentco/set' version 1.0.0 allows attacker to cause a denial of service and may lead to remote code execution.

Q: How urgent is CVE-2020-28267?

Priority 52/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEDOWNGRADE

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

Prototype pollution vulnerability in '@strikeentco/set' version 1.0.0 allows attacker to cause a denial of service and may lead to remote code execution.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

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

Publisher (CNA): Mend · Vendor: set 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-10 16:15 UTCPublished CVE record published
2026-06-17 03:10 UTCUpdated Record last modified

set project set DOWNGRADE

Affected: 1.0.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.0

1. Check installed version

npm ls set

2. No fixed release: DOWNGRADE to a release before 1.0.0

npm view set versions npm install set@"<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-28267?

set: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-28267 being exploited?

CVE-2020-28267 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-28267 affect?

CVE-2020-28267 affects set. Severity is high (CVSS 7.5). Prototype pollution vulnerability in '@strikeentco/set' version 1.0.0 allows attacker to cause a denial of service and may lead to remote code execution.

How urgent is CVE-2020-28267?

Priority 52/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2021-23497 HIGH 7.5 UPGRADE This affects the package @strikeentco/set before 1.0.2

References

← Back to latest CVEs