Vulnerabilities
Summary — last 7 days
New vulnerabilities2,635▼ 214 vs. last week
Critical / high1,385▲ 153 vs. last week
New active exploitation (KEV)7▼ 3 vs. last week
Unscored (no CVSS)56▼ 473 vs. last week
3 results, sorted by published date (most recent first)
| CVE | Status | Severity | EPSS | Active exploitation | Affected technologies | Published ▼ | Modified | Description |
|---|---|---|---|---|---|---|---|---|
| Analyzed | Critical (9.4) | 0.50% | — | Set-in Project Set-in | 2/11/2026 | 6/17/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 mitigate prototype pollution by checking whether user input contained a forbidden key, it is still… | |
| Modified | Critical (9.8) | 1.9% | — | Set-in Project Set-in | 3/17/2022 | 6/17/2026 | 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](https://security.snyk.io/vuln/SNYK-JS-SETIN-1048049) | |
| Modified | Critical (9.8) | 4.0% | — | Set-in Project Set-in | 12/2/2020 | 6/17/2026 | 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. |