How severe is CVE-2023-45822?

CVE-2023-45822 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-45822?

CVE-2023-45822 affects the following packages: github.com/artifacthub/hub (Go). Ecosystems affected: Go.

How do I fix CVE-2023-45822?

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 CVE-2023-45822 is resolved across your whole dependency graph.

How do I detect CVE-2023-45822 in my Go dependencies?

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.

How do I mitigate CVE-2023-45822 if there is no patch (or I can't update yet)?

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.

Is CVE-2023-45822 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-45822 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-45822?

CVE-2023-45822 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 51th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-45822?

CVE-2023-45822 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2023-45822 published, and has it been updated?

CVE-2023-45822 was published on October 19, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

LOW severity

CVE-2023-45822 — hub

LOW

CVE-2023-45822 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.

Unsafe rego built-in allowed in Artifact Hub

Also known asGHSA-9pc8-m4vp-ggvfGO-2023-2134

Published

Oct 19, 2023

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2023-45822.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk

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

1 pkg affected

🐹github.com/artifacthub/hub

Real-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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/artifacthub/hub`	all versions	1.16.0`go get github.com/artifacthub/hub@v1.16.0`

Affected Products

1 product · 1 configurations

Application

hubartifacthub

< 1.16.0

range

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2023-45822 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

O3 Security · Impact-Aware SCA

Is CVE-2023-45822 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

hub

8.2/10

Code-Review10/10

Maintained10/10

Branch-ProtectionN/A

Assessed Nov 9, 2026

Timeline

Disclosed

Oct 19, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2023-45822

GHSA-9pc8-m4vp-ggvf

GO-2023-2134

References

Advisorygithub.com · CVE 2023 45822.json Advisorygithub.com · GHSA 9pc8 m4vp ggvf Advisorynvd.nist.gov · CVE 2023 45822 Webartifacthub.io · artifact hub Webopenpolicyagent.org Webopenpolicyagent.org · latest Webopenpolicyagent.org Packagegithub.com · hub

Related vulnerabilities

Also affects hub

This CVE is low severity; 2 of 2 other CVEs affecting hub are rated as high or higher (top: high).

CVE-2023-45821CVE-2023-45823

Same weakness: CWE-918

This CVE is low severity; 6 of 6 other CVEs with CWE-918 are rated as high or higher (top: moderate).

CVE-2026-126062CVE-2026-79914CVE-2026-88983CVE-2026-28385GHSA-7wpf-ch8f-5f4xCVE-2026-54442Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-45822 — hub

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-45822 in your dependencies?