How severe is CVE-2020-7678?

CVE-2020-7678 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-7678?

CVE-2020-7678 affects the following packages: node-import (npm). Ecosystems affected: npm.

How do I fix CVE-2020-7678?

No patched version of node-import has shipped for CVE-2020-7678 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2020-7678 in my npm dependencies?

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

How do I mitigate CVE-2020-7678 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2020-7678?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2020-7678 can be triaged on real exposure rather than presence alone.

Is CVE-2020-7678 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2020-7678, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-7678?

CVE-2020-7678 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2020-7678 published, and has it been updated?

CVE-2020-7678 was published on July 26, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

CVE-2020-7678 — node-import

CRITICAL

CVE-2020-7678 is a critical-severity (CVSS 9.8) vulnerability in node-import. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

node-import `params` argument can be controlled by users without any sanitization

Published

Jul 26, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

1 known

Exploitation data as of Sep 22, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2020-7678 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

📦node-import

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

This affects all versions of package node-import. The params argument of module function can be controlled by users without any sanitization. This is then provided to the “eval” function located in line 79 in the index file index.js.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-import`	all versions	No fix

Exploits & PoCs

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 all versions of package node-import. The "params" argument …

security.snyk.ioNVDAug 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-import, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of node-import has shipped for CVE-2020-7678 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2020-7678 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2020-7678. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects all versions of package node-import. The `params` argument of module function can be controlled by users without any sanitization. This is then provided to the “eval” function located in line 79 in the index file `index.js`.

O3 Security · Impact-Aware SCA

Is CVE-2020-7678 in your dependencies?

O3 Security finds CVE-2020-7678 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works