CVE-2020-28283: Prototype pollution vulnerability in 'libnested' versions 0.0.0 through 1.5.0 allows an attacker to cause a de

Q: How do I fix CVE-2020-28283?

libnested: upgrade to newer than 1.5.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-28283 being exploited?

CVE-2020-28283 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-28283 affect?

CVE-2020-28283 affects libnested. Severity is critical (CVSS 9.8). 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.

Q: How urgent is CVE-2020-28283?

Priority 66/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-28283 is a critical-severity flaw (CVSS 9.8) affecting libnested. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.4% (top 11%)
CISA exploited list	No
Published	2020-12-29
Last modified	2026-06-17

Publisher (CNA): Mend · Vendor: libnested project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-12-29 18:15 UTCPublished CVE record published
2026-06-17 03:10 UTCUpdated Record last modified

libnested project libnested UPGRADE

Affected: >= 0.0.0 and <= 1.5.0

Fixed in: newer than 1.5.0

Safe to downgrade to: a release before 0.0.0

1. Check installed version

npm ls libnested

2. UPGRADE to newer than 1.5.0

npm install libnested@">1.5.0"

3. If no update is available yet, DOWNGRADE to a release before 0.0.0

npm view libnested versions npm install libnested@"<0.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-28283?

libnested: upgrade to newer than 1.5.0. Exact commands for each OS are on this page.

Is CVE-2020-28283 being exploited?

CVE-2020-28283 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-28283 affect?

CVE-2020-28283 affects libnested. Severity is critical (CVSS 9.8). 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.

How urgent is CVE-2020-28283?

Priority 66/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-25352 HIGH 7.5 UPGRADE The package libnested before 1.5.2 are vulnerable to Prototype Pollution via the set function in index.js

References

← Back to latest CVEs