Mirror Registry For Red Hat Openshift
Approved changes feed: RSS · Atom
cpe:2.3:a:redhat:mirror_registry_for_red_hat_openshift:2.0:*:*:*:*:*:*:*
part: a version: 2.0 update: *
| Vendor | Redhat (e942785a-ca89-506e-bd99-50782639cde3) |
|---|---|
| Product | Mirror Registry For Red Hat Openshift (b599fba8-4508-5e9c-a2c3-9cfcc91adefd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-32591 |
vulnerable | 2026-06-08 07:57:17.724834 |
Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration
MEDIUM (5.2)
A flaw was found in Red Hat Quay's Proxy Cache configuration feature. When an organization administrator configures an upstream registry for proxy caching, Quay makes a network connection to the specified registry hostname without verifying that it points to a legitimate external service. An attacker with organization administrator privileges could supply a crafted hostname to force the Quay server to make requests to internal network services, cloud infrastructure endpoints, or other resources that should not be accessible from the Quay application.
Published: 2026-04-08T17:06:58.222Z
Updated: 2026-07-27T12:05:28.932Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-32590 |
vulnerable | 2026-06-08 07:57:17.724461 |
Mirror-registry: remote code execution using pickle deserialization
HIGH (7.1)
A flaw was found in Red Hat Quay's handling of resumable container image layer uploads. The upload process stores intermediate data in the database using a format that, if tampered with, could allow an attacker to execute arbitrary code on the Quay server.
Published: 2026-04-08T17:04:22.870Z
Updated: 2026-07-19T01:11:17.414Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-32589 |
vulnerable | 2026-06-08 07:57:17.723203 |
Mirror-registry: quay: insecure direct object reference in blobupload
HIGH (7.4)
A flaw was found in Red Hat Quay's container image upload process. An authenticated user with push access to any repository on the registry can interfere with image uploads in progress by other users, including those in repositories they do not have access to. This could allow the attacker to read, modify, or cancel another user's in-progress image upload.
Published: 2026-04-08T17:04:20.284Z
Updated: 2026-07-27T12:05:47.894Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-2377 |
vulnerable | 2026-06-08 07:55:16.980041 |
Mirror-registry: quay: quay: server-side request forgery via log export functionality
MEDIUM (6.5)
A flaw was found in Red Hat Quay and mirror registry for Red Hat OpenShift. The log export feature in these products allows an authenticated user to specify an arbitrary callback URL. A backend process then makes server-side HTTP requests to this provided URL. This vulnerability, known as Server-Side Request Forgery (SSRF), could allow an attacker to send requests from the application's internal network, potentially leading to the disclosure of sensitive information.
Published: 2026-04-08T16:26:07.649Z
Updated: 2026-07-27T12:05:40.006Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-14243 |
vulnerable | 2026-06-08 07:06:34.126677 |
Mirror-registry: openshift mirror registry: user enumeration via authentication error messages
MEDIUM (5.3)
A flaw was found in the OpenShift Mirror Registry. This vulnerability allows an unauthenticated, remote attacker to enumerate valid usernames and email addresses via different error messages during authentication failures and account creation.
Published: 2026-04-08T16:41:55.597Z
Updated: 2026-04-08T21:46:14.175Z |
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.