Set-in Project
Set-in Project Set-in: vulnerabilities and CVEs
Set-in Project Set-in has 3 published vulnerabilities, 1 of them in the last 12 months. 3 are rated critical and 0 are listed by CISA as actively exploited.
CVEs3
Last 12 months1
Critical3
Actively exploited0
All vulnerabilities in the catalogue →⭐ Follow this technology
Latest vulnerabilities
| CVE | Severity | EPSS | Active exploitation | Published | Description |
|---|---|---|---|---|---|
| CVE-2026-26021 | Critical (9.4) | 0.50% | — | Feb 11, 2026 | set-in provides the set value of nested associative structure given array of keys. A prototype pollution vulnerability exists in the the npm package set-in (>=2.0.1, < 2.0.5). Despite a previous fix that attempted to… |
| CVE-2022-25354 | Critical (9.8) | 1.9% | — | Mar 17, 2022 | The package set-in before 2.0.3 are vulnerable to Prototype Pollution via the setIn method, as it allows an attacker to merge object prototypes into it. **Note:** This vulnerability derives from an incomplete fix of… |
| CVE-2020-28273 | Critical (9.8) | 4.0% | — | Dec 2, 2020 | Prototype pollution vulnerability in 'set-in' versions 1.0.0 through 2.0.0 allows attacker to cause a denial of service and may lead to remote code execution. |
🎯 How it gets exploited (ATT&CK techniques)
Number of CVEs of this technology mapped to each exploitation or primary-impact technique.