How severe is GHSA-mm7r-265w-jv6f?

No CVSS score has been assigned to GHSA-mm7r-265w-jv6f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mm7r-265w-jv6f?

GHSA-mm7r-265w-jv6f affects the following packages: @uppy/companion (npm). Ecosystems affected: npm.

How do I fix GHSA-mm7r-265w-jv6f?

Update @uppy/companion to 1.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mm7r-265w-jv6f is resolved across your whole dependency graph.

How do I detect GHSA-mm7r-265w-jv6f in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @uppy/companion. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mm7r-265w-jv6f 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 GHSA-mm7r-265w-jv6f?

O3 pinpoints whether GHSA-mm7r-265w-jv6f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mm7r-265w-jv6f actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-mm7r-265w-jv6f, 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 GHSA-mm7r-265w-jv6f?

GHSA-mm7r-265w-jv6f has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 68th 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.

What type of vulnerability is GHSA-mm7r-265w-jv6f?

GHSA-mm7r-265w-jv6f is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-mm7r-265w-jv6f published, and has it been updated?

GHSA-mm7r-265w-jv6f was published on September 3, 2020 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

GHSA-mm7r-265w-jv6f

GHSA-mm7r-265w-jv6f is a Server-Side Request Forgery (SSRF) vulnerability in @uppy/companion. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-mm7r-265w-jv6f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Server-Side Request Forgery in @uppy/companion

Also known asCVE-2020-8135

Published

Sep 3, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Aug 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% 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.

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.

8other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@uppy/companionnpm

66Kdownloads / week

Description

Versions of @uppy/companion prior to 1.9.3 are vulnerable to Server-Side Request Forgery (SSRF). The get route passes the user-controlled variable req.body.url to a GET request without sanitizing the value. This allows attackers to inject arbitrary URLs and make GET requests on behalf of the server.

Recommendation

Upgrade to version 1.9.3 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@uppy/companion`	all versions	1.9.3

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.

The uppy npm package < 1.9.3 is vulnerable to a Server-Side Request Forg…

hackerone.comNVDMar 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @uppy/companion. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @uppy/companion to 1.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mm7r-265w-jv6f is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-mm7r-265w-jv6f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mm7r-265w-jv6f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `@uppy/companion` prior to 1.9.3 are vulnerable to Server-Side Request Forgery (SSRF). The `get` route passes the user-controlled variable `req.body.url` to a GET request without sanitizing the value. This allows attackers to inject arbitrary URLs and make GET requests on behalf of the server. ## Recommendation Upgrade to version 1.9.3 or later.

O3 Security · Impact-Aware SCA

Is GHSA-mm7r-265w-jv6f in your dependencies?

O3 detects GHSA-mm7r-265w-jv6f across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works