NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2020-28471 — properties-reader

CRITICALFix: steveukx/properties@0877cc8

CVE-2020-28471 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in properties-reader. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for properties-reader — see the affected versions and patch details below.

Properties-Reader before v2.2.0 vulnerable to prototype pollution

Also known asGHSA-jxvf-m3x5-mxwq
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.19%0.78%1.37%1.95%0.7%1.5%May 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

276other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
properties-readernpm
11.2Mdownloads / week

Description

Properties-Reader prior to version 2.2.0 is vulnerable to prototype pollution. Version 2.2.0 contains a patch for this issue.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmproperties-readerall versions2.2.0npm install properties-reader@2.2.0

Affected Products

1 product · 1 configurations
Application
properties-readerproperties-reader_project
< 2.2.0
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

This affects the package properties-reader before 2.2.0.

github.comNVDAug 2022

Report on security.snyk.io

security.snyk.ioNVDAug 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for properties-reader, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update properties-reader to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28471 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Properties-Reader prior to version 2.2.0 is vulnerable to prototype pollution. Version 2.2.0 contains a patch for this issue.
O3 Security · Impact-Aware SCA

Is CVE-2020-28471 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-28471: properties-reader — Fixed in 2.2.0