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

CVE-2020-7684 — rollup-plugin-serve

CRITICALFix: thgh/rollup-plugin-serve@3d144f2

CVE-2020-7684 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in rollup-plugin-serve. A fix is available for rollup-plugin-serve — see the affected versions and patch details below.

Path traversal in rollup-plugin-serve

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 6, 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 CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk
0.07%0.70%1.34%1.97%0.6%1.5%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-7684 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.

233other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
rollup-plugin-servenpm
80Kdownloads / week

Description

Path traversal in npm package rollup-plugin-serve before version 1.0.2. There is no path sanitization in readFile operation.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmrollup-plugin-serveall versions1.0.2npm install rollup-plugin-serve@1.0.2

Affected Products

1 product · 1 configurations
Application
rollup-plugin-serverollup-plugin-serve_project
all

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update rollup-plugin-serve to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7684 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Path traversal in npm package `rollup-plugin-serve` before version 1.0.2. There is no path sanitization in `readFile` operation.
O3 Security · Impact-Aware SCA

Is CVE-2020-7684 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-7684: rollup-plugin — Fixed in 1.0.2