dbcve.org
Mirror Registry For Red Hat OpenshiftApplication · Redhat

CVE-2026-32591

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in Red Hat Quay's Proxy Cache feature. When an organization administrator configures an upstream registry for proxy caching, Quay connects to the user-supplied hostname without validating whether it points to a legitimate external service. An attacker with org admin privileges could supply crafted hostnames to force Quay to make requests to internal network services, cloud metadata endpoints, or other internal resources that should not be exposed.

MitigationImplement strict hostname allowlisting/validation for proxy cache configurations to ensure only approved external registries can be used, and apply network segmentation to restrict Quay server outbound connections to internal infrastructure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mirror Registry For Red Hat OpenshiftApplication
Affected:all versions= 2.0
QuayApplication
Affected:= 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Proxy Cache is enabled
    In the Quay management console, navigate to Organization settings or check the configuration file (config.yaml) for 'FEATURE_PROXY_CACHE' set to true. Alternatively, query the Quay API endpoint /api/v1/config/featureflags to see if proxy_cache is listed as enabled.
    Affected if Proxy Cache feature is enabled in the Quay or Mirror Registry configuration
  2. Check the installed Quay version
    Run 'docker exec -it quay-enterprise-name quay version' or check the deployment manifest for the Quay container image tag. For Mirror Registry, run 'cat /etc/quay-registry/quay.yaml' or check the RPM version with 'rpm -q quay-mirror-registry'.
    Affected if The installed version is Redhat Quay 3.0.0 or Redhat Mirror Registry 2.0, or any version of Mirror Registry since all versions are affected
  3. Verify if organization administrator role exists
    Review user role assignments in the Quay UI under Organization > Members, or query the API endpoint /api/v1/organization/{orgname}/members to list users with admin privileges within any organization.
    Affected if Any user possesses organization administrator privileges, which would enable them to configure proxy cache settings for their organization
  4. Check for proxy cache endpoint configuration
    Query the API endpoint /api/v1/repository or inspect the organization configuration for any repository that has proxy cache to an upstream registry configured. Look for entries with 'proxy' : { 'cache_upstream' : ... } in the repository or organization settings.
    Affected if A proxy cache is configured pointing to any upstream registry URL, which would indicate the vulnerable code path is in use

A user is affected if they have Red Hat Quay 3.0.0 or Red Hat Mirror Registry 2.0 (any version) with the Proxy Cache feature enabled and an organization administrator can configure proxy cache upstream hostnames.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict hostname allowlisting/validation for proxy cache configurations to ensure only approved external registries can be used, and apply network segmentation to restrict Quay server outbound connections to internal infrastructure.

Fix this in Mirror Registry For Red Hat Openshift Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32591 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32591 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data