CVE-2022-0086 json
Server-Side Request Forgery (SSRF) in transloadit/uppy
published 4y ago modified 4mo ago also GHSA-x8rq-rc7x-5fg5 , EUVD-2022-0738
- cvss
- 8.2
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
uppy is vulnerable to Server-Side Request Forgery (SSRF)
Patch / fix
- npm @uppy/companion 3.1.5
- transloadit transloadit/uppy 2.3.3
Is CVE-2022-0086 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.25% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/c1c03ef6-3f18-4976-a9ad-08c251279122 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.2 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 8.2 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @uppy/companion | <3.1.5 |
3.1.5 |
Affected products
- transloadit transloadit/uppy
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/transloadit/uppy/commit/fc137e30a2a3102eb191141f280d5de20dacdf8f
web, patch, third-party-advisory
-
huntr.dev
/bounties/c1c03ef6-3f18-4976-a9ad-08c251279122
web, exploit, patch, third-party-advisory
-
github.com
/transloadit/uppy/pull/3403
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-0086
advisory
-
github.com
/transloadit/uppy
web
-
github.com
/transloadit/uppy/releases/tag/uppy%402.3.3
web
Sources
- CVE List CVE-2022-0086
- GitHub Advisory GHSA-x8rq-rc7x-5fg5
- NVD CVE-2022-0086
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.