Approved changes feed: RSS · Atom

cpe:2.3:a:artifacthub:hub:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorArtifacthub (b88cb07a-f235-5f1b-9743-8b961d24bc84)
ProductHub (10a13044-c9e9-5fe0-9ecf-106ec900f100)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/artifacthub/hub purl2cpe 2026-06-01 10:15:37.724062

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-45823 vulnerable 2026-06-08 06:12:43.410015 Arbitrary file read in Artifact Hub
HIGH (7.5)
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 by using symbolic links in certain kinds of repositories loaded into Artifact Hub, it was possible to read internal files. Artifact Hub indexes content from a variety of sources, including git repositories. When processing git based repositories, Artifact Hub clones the repository and, depending on the artifact kind, reads some files from it. During this process, in some cases, no validation was done to check if the file was a symbolic link. This made possible to read arbitrary files in the system, potentially leaking sensitive information. This issue has been resolved in version `1.16.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Published: 2023-10-19T20:53:40.382Z
Updated: 2024-09-12T17:45:40.855Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-45822 vulnerable 2026-06-08 06:12:43.409413 Unsafe rego built-in allowed in Artifact Hub
LOW (3.7)
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.
Published: 2023-10-19T20:53:36.298Z
Updated: 2024-09-12T17:45:57.658Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-45821 vulnerable 2026-06-08 06:12:43.408835 Incorrect Docker Hub registry check in Artifact Hub
MEDIUM (5.4)
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 the `registryIsDockerHub` function was only checking that the registry domain had the `docker.io` suffix. Artifact Hub allows providing some Docker credentials that are used to increase the rate limit applied when interacting with the Docker Hub registry API to read publicly available content. Due to the incorrect check described above, it'd be possible to hijack those credentials by purchasing a domain which ends with `docker.io` and deploying a fake OCI registry on it. <https://artifacthub.io/> uses some credentials that only have permissions to read public content available in the Docker Hub. However, even though credentials for private repositories (disabled on `artifacthub.io`) are handled in a different way, other Artifact Hub deployments could have been using them for a different purpose. This issue has been resolved in version `1.16.0`. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Published: 2023-10-19T20:53:34.802Z
Updated: 2024-09-12T17:47:02.040Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.