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

CVE-2020-7715 — deep-get-set

CRITICALFix: acstll/deep-get-set@a127e65

CVE-2020-7715 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in deep-get-set. 1 public exploit reference exists, so weaponization risk is real. A fix is available for deep-get-set — see the affected versions and patch details below.

Prototype Pollution in deep-get-set

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

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk
0.30%1.02%1.74%2.47%0.8%2.0%Apr 26Aug 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,386 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
📦deep-get-set

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

All versions of package deep-get-set prior to version 1.1.1 are vulnerable to Prototype Pollution via the main function.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdeep-get-setall versions1.1.1npm install deep-get-set@1.1.1

Affected Products

1 product · 1 configurations
Application
deep-get-setdeep-get-set_project
all
Exploits & PoCs
1

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 deep-get-set are vulnerable to Prototype Polluti…

snyk.ioNVDJul 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update deep-get-set to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7715 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 deep-get-set prior to version 1.1.1 are vulnerable to Prototype Pollution via the main function.
O3 Security · Impact-Aware SCA

Is CVE-2020-7715 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works