CVE-2020-28272: Prototype pollution vulnerability in 'keyget' versions 1.0.0 through 2.2.0 allows attacker to cause a denial o

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

keyget: upgrade to newer than 2.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-28272 being exploited?

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

CVE-2020-28272 affects keyget. Severity is critical (CVSS 9.8). Prototype pollution vulnerability in 'keyget' versions 1.0.0 through 2.2.0 allows attacker to cause a denial of service and may lead to remote code execution.

Q: How urgent is CVE-2020-28272?

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

This week

CRITICAL 9.8REMOTEUPGRADE

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

Prototype pollution vulnerability in 'keyget' versions 1.0.0 through 2.2.0 allows 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-02
Last modified	2026-06-17

Publisher (CNA): Mend · Vendor: keyget 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-02 15:15 UTCPublished CVE record published
2026-06-17 03:10 UTCUpdated Record last modified

keyget project keyget UPGRADE

Affected: >= 1.0.1 and <= 2.2.0

Fixed in: newer than 2.2.0

Safe to downgrade to: a release before 1.0.1

1. Check installed version

npm ls keyget

2. UPGRADE to newer than 2.2.0

npm install keyget@">2.2.0"

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

npm view keyget versions npm install keyget@"<1.0.1"

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-28272?

keyget: upgrade to newer than 2.2.0. Exact commands for each OS are on this page.

Is CVE-2020-28272 being exploited?

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

CVE-2020-28272 affects keyget. Severity is critical (CVSS 9.8). Prototype pollution vulnerability in 'keyget' versions 1.0.0 through 2.2.0 allows attacker to cause a denial of service and may lead to remote code execution.

How urgent is CVE-2020-28272?

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

Related CVEs

CVE-2021-23760 MEDIUM 5.6 MITIGATE The package keyget from 0.0.0 are vulnerable to Prototype Pollution via the methods set, push, and at which co

References

← Back to latest CVEs