How to Fix CVE-2026-32589: Red Hat Quay 3.16 (Bundle Sibling)
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 7.4, High |
|---|---|
| Actively exploited? | No |
| Affected | Red Hat Quay 3.16 (1779204086 < *); mirror registry for Red Hat OpenShift (see advisory); mirror registry for Red Hat OpenShift 2 (see advisory) |
| Fixed in | Same patched build as CVE-2026-2377 |
| Type (CWE) | CWE-639: Authorization Bypass Through User-Controlled Key |
CVE-2026-32589 is a sibling vulnerability in the same Red Hat Red Hat Quay 3.16 advisory bundle as CVE-2026-2377. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-32589 matches the primary write-up.
What is different about CVE-2026-32589?
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.
Impact is consistent with the bundle: compromise of the affected component as described in the vendor advisory. The patched build closes every code path in the advisory in one update.
How to fix CVE-2026-32589
Apply the patched build per the primary write-up: How to Fix CVE-2026-2377.
For a quick check, confirm the running version of Red Hat Quay 3.16:
# Confirm the installed version via your package manager
dpkg -l | grep -i red # Debian/Ubuntu
rpm -qa | grep -i red # RHEL/CentOS/Rocky
Frequently asked questions
Is CVE-2026-32589 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-32589?
CVSS rates it 7.4 (High). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take Red Hat Quay 3.16 offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-32589 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://access.redhat.com/errata/RHSA-2026:19375
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-32589
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-2377
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Red Hat Red Hat Quay 3.16 advisory bundle. Full procedure at how-to-fix-cve-2026-2377.*