set-in
npm3 known CVEs affecting this package
Aggregated from OSV, GitHub Security Advisories, NVD, and vendor advisories. Each CVE links to its full detail page with vendor advisories, patches, fixed versions, and remediation guidance.
CVEs affecting set-inpage 1 of 1
- CVE-2020-28273CRITICALCVSS 9.8EG 9.8✓ Fixed in 2.0.12020-12-02
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.
- CVE-2022-25354HIGHCVSS 8.6EG 8.6✓ Fixed in 2.0.32022-03-17
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:…
- CVE-2026-26021CRITICALCVSS 9.8EG 9.8✓ Fixed in 2.0.52026-02-11
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 pol…
Check whether set-in is used in your infrastructure
EchelonGraph scans your cloud and SBOMs to map every package to your actual deployments. See blast radius for set-in CVEs against the assets you own.
Start Free Scan →