Artifact Hub allows unsafe rego built-inGHSA-9pc8-m4vp-ggvf
LOWGHSA-9pc8-m4vp-ggvf is a low-severity (CVSS 3.7) Server-Side Request Forgery (SSRF) vulnerability in github.com/artifacthub/hub. A fix is available for github.com/artifacthub/hub — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- 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-9pc8-m4vp-ggvf.
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/artifacthub/hubReal-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
Impact
During a security audit of Artifact Hub's code base, a security researcher at OffSec identified a bug in which a default unsafe rego built-in was allowed to be used when defining authorization policies.
Artifact Hub includes a fine-grained authorization mechanism that allows organizations to define what actions can be performed by their members. It is based on customizable authorization policies that are enforced by the Open Policy Agent. Policies are written using rego and their data files are expected to be json documents. By default, rego allows policies to make HTTP requests, which can be abused to send requests to internal resources and forward the responses to an external entity. In the context of Artifact Hub, this capability should have been disabled.
Patches
This issue has been resolved in version 1.16.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/artifacthub/hub | all versions | 1.16.0go get github.com/artifacthub/hub@v1.16.0 |
Affected Products
hubartifacthubDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/artifacthub/hub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/artifacthub/hub to 1.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9pc8-m4vp-ggvf 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-9pc8-m4vp-ggvf in your dependencies?
Find it across Go, including transitive dependencies.