Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2020-28442 — js-data

CRITICALFix: js-data/js-data#574

CVE-2020-28442 is a critical-severity (CVSS 9.8) vulnerability in js-data. 3 public exploit references exist, so weaponization risk is real. A fix is available for js-data — see the affected versions and patch details below.

Prototype Pollution in js-data

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk+1.35%
Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk
0.13%0.92%1.70%2.48%0.6%2.0%Apr 26Oct 26

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

How urgent is this, really

CVE-2020-28442 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

67other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
js-datanpm
5Kdownloads / week

Description

All versions of package js-data prior to 3.0.10 are vulnerable to Prototype Pollution via the deepFillIn function.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmjs-dataall versions3.0.10npm install js-data@3.0.10

Affected Products

1 product · 1 configurations
Application
js-datajs-data
all
Exploits & PoCs
3

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

All versions of package js-data are vulnerable to Prototype Pollution vi…

snyk.ioNVDDec 2020

All versions of package js-data are vulnerable to Prototype Pollution vi…

snyk.ioNVDDec 2020

All versions of package js-data are vulnerable to Prototype Pollution vi…

snyk.ioNVDDec 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update js-data to 3.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28442 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

All versions of package js-data prior to 3.0.10 are vulnerable to Prototype Pollution via the `deepFillIn` function.
O3 Security · Impact-Aware SCA

Is CVE-2020-28442 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-28442: js-data — Fixed in 3.0.10