CVE-2020-8116: Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1

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

dot-prop: upgrade to 4.2.1, 5.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-8116 being exploited?

CVE-2020-8116 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-8116 affect?

CVE-2020-8116 affects dot-prop. Severity is high (CVSS 7.3). Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.

Q: How urgent is CVE-2020-8116?

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

This week

HIGH 7.3REMOTEUPGRADE

CVE-2020-8116 is a high-severity flaw (CVSS 7.3) affecting dot-prop. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.1% (top 12%)
CISA exploited list	No
Weakness	CWE-471, CWE-1321
Published	2020-02-04
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: dot-prop project

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

Am I affected?

Timeline

2020-02-04 20:15 UTCPublished CVE record published
2026-06-17 03:25 UTCUpdated Record last modified

dot-prop project dot-prop UPGRADE

Affected: < 4.2.1 · >= 5.0.0 and < 5.1.1

Fixed in: 4.2.1, 5.1.1

Safe to downgrade to: a release before 5.0.0

1. Check installed version

npm ls dot-prop

2. UPGRADE to 4.2.1

npm install dot-prop@">=4.2.1"

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

npm view dot-prop versions npm install dot-prop@"<5.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-8116?

dot-prop: upgrade to 4.2.1, 5.1.1. Exact commands for each OS are on this page.

Is CVE-2020-8116 being exploited?

CVE-2020-8116 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-8116 affect?

CVE-2020-8116 affects dot-prop. Severity is high (CVSS 7.3). Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.

How urgent is CVE-2020-8116?

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

Software pages

npm packages vulnerabilities

References

← Back to latest CVEs