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

CVE-2020-8205 — @uppy/companion

HIGHFix: transloadit/uppy#2322

CVE-2020-8205 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in @uppy/companion. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @uppy/companion — see the affected versions and patch details below.

Server-Side Request Forgery in @uppy/companion

Also known asGHSA-9m4x-8w29-r78g
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk
0.00%0.56%1.13%1.69%0.3%1.2%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2020-8205 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

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.

8other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@uppy/companionnpm
55Kdownloads / week

Description

The uppy npm package < 1.13.2 and < 2.0.0-alpha.5 is vulnerable to a Server-Side Request Forgery (SSRF) vulnerability, which allows an attacker to scan local or external networks or otherwise interact with internal systems.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npm@uppy/companionall versions1.13.2npm install @uppy/companion@1.13.2
📦npm@uppy/companion≥ 2.0.0-alpha.0&&< 2.0.0-alpha.52.0.0-alpha.5npm install @uppy/companion@2.0.0-alpha.5

Affected Products

1 product · 6 configurations
Application
uppytransloadit
< 1.13.2
1 version
2.0.0
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.

The uppy npm package < 1.13.2 and < 2.0.0-alpha.5 is vulnerable to a Ser…

hackerone.comNVDJul 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 @uppy/companion, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @uppy/companion to 1.13.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-8205 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

The uppy npm package < 1.13.2 and < 2.0.0-alpha.5 is vulnerable to a Server-Side Request Forgery (SSRF) vulnerability, which allows an attacker to scan local or external networks or otherwise interact with internal systems.
O3 Security · Impact-Aware SCA

Is CVE-2020-8205 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-8205: @uppy/companion SSRF — Fixed in 1.13.2