# CVE-2026-32589: Mirror-registry: quay: insecure direct object reference in blobupload

> An authenticated user can interfere with other users' image uploads, allowing unauthorized reading, modification, or cancellation of in-progress uploads.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-7fjh-cgxv-cjc6

## What is CVE-2026-32589?

CVE-2026-32589 is a high-severity missing authorization vulnerability in Red Hat Quay 3.10, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in Red Hat Quay's container image upload process. An authenticated user with push access to any repository on the registry can interfere with image uploads in progress by other users, including those in repositories they do not have access to. This could allow the attacker to read, modify, or cancel another user's in-progress image upload.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 2 products.


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

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

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

## Is CVE-2026-32589 being exploited?

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

## Other vulnerabilities in Red Hat Quay 3.10

- [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)
- [CVE-2026-32591](https://insights.sbomify.com/CVE-2026-32591/): Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration (medium 5.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32589 is a high-severity missing authorization vulnerability in Red Hat Quay 3.10, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32589 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-32589/ (Markdown: https://insights.sbomify.com/CVE-2026-32589/index.md)
```

## Sources

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

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