Artifact Hub allows unsafe rego built-in

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2023-45822: 0.64% estimated exploitation activity in the next 30 days; percentile 50.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

19 Oct 2023, 17:05 UTC

Last modified by the source

6 Nov 2023, 05:01 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9pc8-m4vp-ggvf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-45822

Advisory: Artifact Hub allows unsafe rego built-in
IDs: CVE-2023-45822, GHSA-9pc8-m4vp-ggvf
Record: https://patchnext.com/advisories/cve-2023-45822 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/artifacthub/hub 1.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/artifacthub/hub: affected < 1.16.0; fixed in 1.16.0

## Suggested inspection (read-only)
- Go github.com/artifacthub/hub: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/artifacthub/hub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9pc8-m4vp-ggvf (GitHub-reviewed advisory GHSA-9pc8-m4vp-ggvf lists affected ranges: Go github.com/artifacthub/hub >=0 <1.16.0)

Commands are suggestions: review each one before running it.