CVE-2020-8135: Server-Side Request Forgery in @uppy/companion
Summary
CVE-2020-8135: Server-Side Request Forgery in @uppy/companion. Affects @uppy/companion versions < 1.9.3. Fixed in 1.9.3. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @uppy/companion package is an open-source library that provides server-side support for file uploading in web applications. It is commonly used to handle file uploads securely and efficiently. However, versions prior to 1.9.3 are vulnerable to a Server-Side Request Forgery (SSRF) attack.
Vulnerability Detail
The vulnerability in @uppy/companion arises from the get route, which passes the user-controlled variable req.body.url to a GET request without proper sanitization. This allows an attacker to inject arbitrary URLs and make GET requests on behalf of the server. An attacker could exploit this vulnerability to access internal resources, bypass security measures, or perform other malicious activities.
How To Fix
Latest published version: 7.2.0 as of 22 Oct 2026
npm install @uppy/companion@7.2.0Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.9.3
This is the first release that contains the fix.
npm install @uppy/companion@1.9.3Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
The vulnerability in @uppy/companion allows for Server-Side Request Forgery (SSRF) attacks, which can lead to unauthorized access and other malicious activities. It is crucial to upgrade to version 1.9.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for @uppy/companion →
FAQ
Server-Side Request Forgery (SSRF) is a vulnerability that allows an attacker to make requests from the server to arbitrary URLs, potentially accessing internal resources or bypassing security measures.
This vulnerability in @uppy/companion could allow an attacker to perform unauthorized actions on behalf of the server, potentially leading to data breaches, unauthorized access, or other malicious activities.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will provide real-time alerts for open-source vulnerabilities.
Currently, there are no known workarounds for this vulnerability. It is recommended to upgrade to the fixed version of @uppy/companion to mitigate the risk.
You can find more information about this vulnerability in the GitHub Advisory Database (https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/09/GHSA-mm7r-265w-jv6f/GHSA-mm7r-265w-jv6f.json).
Related vulnerabilities
Recent vulnerabilities recorded for @uppy/companion.
