Paranoidhttp Server-Side Request Forgery vulnerabilityGHSA-v9mp-j8g7-2q6m
HIGHFix: hakobe/paranoidhttp@07f671dGHSA-v9mp-j8g7-2q6m is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in github.com/hakobe/paranoidhttp. A fix is available for github.com/hakobe/paranoidhttp — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-v9mp-j8g7-2q6m.
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/hakobe/paranoidhttpReal-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
Paranoidhttp before 0.3.0 allows SSRF because [::] is equivalent to the 127.0.0.1 address, but does not match the filter for private addresses.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hakobe/paranoidhttp | all versions | 0.3.0go get github.com/hakobe/paranoidhttp@v0.3.0 |
Affected Products
paranoidhttpparanoidhttp_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hakobe/paranoidhttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hakobe/paranoidhttp to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v9mp-j8g7-2q6m 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-v9mp-j8g7-2q6m in your dependencies?
Find it across Go, including transitive dependencies.