CVE-2026-32591

Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration

Published Apr 8, 2026 CVSS 3.1 · 5.2 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Quay’s proxy‑cache feature allows an organization administrator to specify an upstream registry for caching. The application does not validate the supplied hostname, allowing the administrator to provide a crafted address that forces Quay to establish an outgoing connection to any target reachable from the Quay host. Consequently, sensitive internal services, cloud‑infrastructure endpoints, and other normally protected resources may be queried or even accessed by the attacker. This vulnerability enables the exfiltration of private data or the exploitation of services that are not intended to be exposed, representing a moderate‑severity security risk. The weakness is identified as a server‑side request forgery (CWE‑918).

Affected Systems

Red Hat Quay version 3 and the Red Hat mirror registry components for OpenShift, including mirror registry 1 and mirror registry 2. These components are commonly deployed on OpenShift clusters and are responsible for handling container image distribution and caching.

Risk and Exploitability

The CVSS score of 5.2 indicates moderate severity, and the exploit requires organization‑administrator privileges to inject the malicious hostname. Because the attack vector is not publicly reachable without privileged configuration access, the overall risk is moderate, with some dependency on internal access controls. No publicly available exploit data or KEV listing is present, and EPSS data is not available. The risk is mainly driven by the lack of hostname validation and the potential to reach unintended internal resources.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Check the Red Hat security announcement linked in the CVE references and apply the vendor‑supplied patch or upgrade to the latest Quay or mirror registry version that removes the vulnerability.
  • If a patch is not yet available, restrict organization‑administrator privileges so that only trusted individuals can configure proxy cache upstream registries.
  • Consider disabling the proxy cache feature or enforcing a whitelist of allowed upstream registry hostnames to prevent arbitrary outbound connections.

Generated by OpenCVE AI on April 8, 2026 at 18:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:/a:redhat:quay:3 cpe:/a:redhat:quay:3.9::el8
References
Type Values Removed Values Added
CPEs cpe:/a:redhat:quay:3.16::el9 cpe:/a:redhat:quay:3
References
Type Values Removed Values Added
CPEs cpe:/a:redhat:quay:3 cpe:/a:redhat:quay:3.14::el8
References
Type Values Removed Values Added
First Time appeared Redhat mirror Registry For Red Hat Openshift
CPEs cpe:2.3:a:redhat:mirror_registry_for_red_hat_openshift:-:*:*:*:*:*:*:*
cpe:2.3:a:redhat:mirror_registry_for_red_hat_openshift:2.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:quay:3.0.0:*:*:*:*:*:*:*
Vendors & Products Redhat mirror Registry For Red Hat Openshift
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration
First Time appeared Redhat
Redhat mirror Registry
Redhat quay
Weaknesses CWE-918
CPEs cpe:/a:redhat:mirror_registry:1
cpe:/a:redhat:mirror_registry:2
cpe:/a:redhat:quay:3
Vendors & Products Redhat
Redhat mirror Registry
Redhat quay
References
Metrics cvssV3_1

{'score': 5.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Nov 12, 2026, 11:43 PM
Reserved
Mar 12, 2026, 2:39 PM
Status
Modified
Published
Apr 8, 2026, 6:26 PM
Modified
Nov 13, 2026, 12:20 AM
Severity
Important
Public date
Apr 8, 2026, 12:00 AM