CVE-2020-28267 is a high-severity (CVSS 7.5) remote code execution vulnerability in @strikeentco/set. A fix is available for @strikeentco/set — see the affected versions and patch details below.
Prototype pollution in @strikeentco/set
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@strikeentco/setnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @strikeentco/set | ≥ 1.0.0&&< 1.0.1 | 1.0.1npm install @strikeentco/set@1.0.1 |
Affected Products
setset_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strikeentco/set, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @strikeentco/set to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28267 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2020-28267 in your dependencies?
Find it across npm, including transitive dependencies.