SSRF (Server-Side Request Forgery) in Red Hat Quay's Proxy Cache configuration feature (CVE-2026-32591)
Summary
SSRF in Red Hat Quay's Proxy Cache configuration feature (CVE-2026-32591). Confidential information can be exposed externally.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32591 has been found in Red Hat Quay's Proxy Cache configuration feature.
Confidential information can be exposed externally. CVSS score: 5.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Red Hat Quay's Proxy Cache configuration feature CVE-2026-32591" on the vendor's site.
CVE-2026-32591 (Red Hat Quay's Proxy Cache configuration feature) — CWE-918 / CVSS v3 5.2
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in Red Hat Quay's Proxy Cache configuration feature.
Check the vendor advisory for the affected versions of Red Hat Quay's Proxy Cache configuration feature.
Severity: Medium (CVSS 5.2/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Red Hat Quay's Proxy Cache configuration feature を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web access.redhat.com
- web access.redhat.com
- web bugzilla.redhat.com
- web nvd.nist.gov
- web github.com
- web access.redhat.com
- web access.redhat.com
- web security.access.redhat.com
- web access.redhat.com
- web access.redhat.com
- web access.redhat.com
- web access.redhat.com
- web access.redhat.com
- web access.redhat.com
- web access.redhat.com
- web access.redhat.com