ProxyScotch is vulnerable to a server-side Request Forgery (SSRF)GHSA-5hjh-c26m-xw8w
HIGHFix: hoppscotch/proxyscotch@de67380GHSA-5hjh-c26m-xw8w is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in github.com/hoppscotch/proxyscotch. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/hoppscotch/proxyscotch — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/hoppscotch/proxyscotchReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
ProxyScotch is a simple proxy server created for hoppscotch.io. The package github.com/hoppscotch/proxyscotch before 1.0.0 are vulnerable to Server-side Request Forgery (SSRF) when interceptor mode is set to proxy. It occurs when an HTTP request is made by a backend server to an untrusted URL submitted by a user. It leads to a leakage of sensitive information from the server.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hoppscotch/proxyscotch | all versions | 1.0.0go get github.com/hoppscotch/proxyscotch@v1.0.0 |
Affected Products
proxyscotchproxyscotch_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hoppscotch/proxyscotch, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hoppscotch/proxyscotch to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5hjh-c26m-xw8w is resolved across your whole dependency graph.
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
Is GHSA-5hjh-c26m-xw8w in your dependencies?
Find it across Go, including transitive dependencies.