Libnested is a narrowly scoped library project with a focused vulnerability footprint centered on its core library product, where the durable signal involves prototype pollution and related object-attribute manipulation weaknesses. These issues are characteristic of dynamic language implementations and reflect the attack surface presented by unvalidated modifications to object prototypes. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Libnested Project over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-28283CRITICAL Prototype pollution vulnerability in 'libnested' versions 0.0.0 through 1.5.0 allows an attacker to cause a denial of service and may lead to remote code execution. | Dec 29, 2020 | 9.8 | 30 | NO | NO |
CVE-2022-25352CRITICAL The package libnested before 1.5.2 are vulnerable to Prototype Pollution via the set function in index.js. **Note:** This vulnerability derives from an incomplete fix for [CVE-2020 | Mar 17, 2022 | 9.8 | 24 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Libnested Project.
Media articles that mention a CVE ID that affects a product developed by Libnested Project — matched by CVE ID, not by vendor name.