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

CVE-2020-7708 — irrelon-path

CRITICALFix: Irrelon/irrelon-path@8a126b1

CVE-2020-7708 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in irrelon-path. 2 public exploit references exist, so weaponization risk is real. A fix is available for irrelon-path — see the affected versions and patch details below.

Prototype Pollution in irrelon-path and @irrelon/path

Also known asGHSA-j7cg-h9v9-6vqp
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
2 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
0.56%1.49%2.42%3.34%1.1%2.8%Apr 26Aug 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

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

Real-World Exposure

2 pkgs 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.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
irrelon-pathnpm
19downloads / week
@irrelon/pathnpm
809downloads / week

Description

The package irrelon-path before 4.7.0; the package @irrelon/path before 4.7.0 are vulnerable to Prototype Pollution via the set, unSet, pushVal and pullVal functions.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmirrelon-pathall versions4.7.0npm install irrelon-path@4.7.0
📦npm@irrelon/pathall versions4.7.0npm install @irrelon/path@4.7.0

Affected Products

2 products · 2 configurations
Application
\@irrelon\/pathirrelon
< 4.7.0
range
Application
irrelon-pathirrelon
< 4.7.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.

The package irrelon-path before 4.7.0; the package @irrelon/path before …

snyk.ioNVDDec 2022

The package irrelon-path before 4.7.0; the package @irrelon/path before …

snyk.ioNVDDec 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 irrelon-path, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

The package irrelon-path before 4.7.0; the package @irrelon/path before 4.7.0 are vulnerable to Prototype Pollution via the set, unSet, pushVal and pullVal functions.
O3 Security · Impact-Aware SCA

Is CVE-2020-7708 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-7708: irrelon-path — Fixed in 4.7.0