Set-In Project Set-In vulnerabilities
3 known vulnerabilities affecting set-in_project/set-in.
Total CVEs
3
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL3
Vulnerabilities
Page 1 of 1
CVE-2026-26021P3CRITICALCVSS 9.8≥ 2.0.1, < 2.0.52026-02-11
CVE-2026-26021 [CRITICAL] CWE-1321 CVE-2026-26021: set-in provides the set value of nested associative structure given array of keys. A prototype pollu
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 possible to pollute Object.proto
ghsanvdosv
CVE-2022-25354P3CRITICALCVSS 9.8fixed in 2.0.32022-03-17
CVE-2022-25354 [CRITICAL] CVE-2022-25354: The package set-in before 2.0.3 are vulnerable to Prototype Pollution via the setIn method, as it al
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)
ghsanvdosv
CVE-2020-28273P3CRITICALCVSS 9.8≥ 1.0.0, ≤ 2.0.0≥ unspecified, < 2.0.32020-12-02
CVE-2020-28273 [CRITICAL] CVE-2020-28273: Prototype pollution vulnerability in 'set-in' versions 1.0.0 through 2.0.0 allows attacker to cause
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.
ghsanvdosv