CVE-2026-32589
Mirror-registry: quay: insecure direct object reference in blobupload
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- openshift/mirror-registry-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-rhel8
Version range not reported
- openshift/mirror-registry-rhel8
Version range not reported