CVE-2023-45822 [Low] | Security Vulnerability in Hub

Artifact Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. During a security audit of Artifact Hub's code base a security researcher 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. This issue has been resolved in version `1.16.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.09%	0.52%	+0.43%
2	2025-11-21	0.25%	0.09%	-0.15%
3	2025-11-18	—	0.25%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.09%

0.52%

+0.43%

2025-11-21

0.25%

0.09%

-0.15%

2025-11-18

—

0.25%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.7	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.2	1.4	[email protected]
5.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	3.9	1.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.7

3.1

LOW

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.2

1.4

[email protected]

5.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

3.9

1.4

[email protected]

Affected software / configurations for CVE-2023-45822

Vendor	Product	Version	Raw CPE
artifacthub	hub	< 1.16.0	cpe:2.3:a:artifacthub:hub::::::::

References for CVE-2023-45822

URL	Tags
https://artifacthub.io/packages/helm/artifact-hub/artifact-hub?modal=changelog&version=1.16.0	Product
https://github.com/artifacthub/hub/security/advisories/GHSA-9pc8-m4vp-ggvf	Third Party Advisory
https://www.openpolicyagent.org/	Mitigation
https://www.openpolicyagent.org/docs/latest/#rego	Mitigation

URL

CVE-2023-45822 | Unsafe rego built-in allowed in Artifact Hub

Exploit prediction scoring system (EPSS) score for CVE-2023-45822

Common vulnerability scoring system (CVSS) metrics for CVE-2023-45822

Weakness enumeration for CVE-2023-45822

GitHub Security Advisory for CVE-2023-45822

Affected software / configurations for CVE-2023-45822

References for CVE-2023-45822