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

> An organization administrator can exploit proxy cache configuration to force the Quay server to access internal network resources via server-side request forgery.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-9wjq-f6rc-86wf

## What is CVE-2026-32591?

CVE-2026-32591 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3.10, published on 8 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

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

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-32591?

It affects 2 products.


Products: Redhat Mirror Registry for Red Hat Openshift, Redhat Quay.

## How do I fix CVE-2026-32591?

No fix has been published for CVE-2026-32591 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32591 being exploited?

There is no known exploitation of CVE-2026-32591 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat Quay 3.10

- [CVE-2026-32589](https://insights.sbomify.com/CVE-2026-32589/): Mirror-registry: quay: insecure direct object reference in blobupload (high 7.4)
- [CVE-2026-32590](https://insights.sbomify.com/CVE-2026-32590/): Mirror-registry: remote code execution using pickle deserialization (high 7.1)
- [CVE-2026-2377](https://insights.sbomify.com/CVE-2026-2377/): Mirror-registry: quay: quay: server-side request forgery via log export functionality (medium 6.5)
- [CVE-2025-14243](https://insights.sbomify.com/CVE-2025-14243/): Mirror-registry: openshift mirror registry: user enumeration via authentication error messages (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32591 and fix it if it is affected.

What it is: CVE-2026-32591 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3.10, published on 8 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32591 in the wild and no public exploit code.

Affected product: Red Hat Quay 3.10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32591/ (Markdown: https://insights.sbomify.com/CVE-2026-32591/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32591
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32591
- OSV: https://osv.dev/vulnerability/CVE-2026-32591

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32591/
Summaries are generated and may contain mistakes; the official description above is the record.