CVE Intelligence
High Access control

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

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.

Published Apr 8, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.43%
ahead of 35% of scored CVEs · Oct 14, 2026
Affects
Red Hat
Mirror Registry For Red Hat Openshift and 9 more
CVSS base
7.4
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Red Hat Mirror Registry For Red Hat Openshift, Red Hat mirror registry for Red Hat OpenShift 2.0, Red Hat Quay…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Red Hat Mirror Registry For Red Hat Openshift versions not specified by the sourceversion 2.0 Vulnerable NIST National Vulnerability Database
Red Hat Mirror Registry For Red Hat Openshift versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat mirror registry for Red Hat OpenShift 2.0 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Quay version 3.0.0 Vulnerable NIST National Vulnerability Database
Red Hat Red Hat Quay 3.10 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Quay 3.12 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Quay 3.14 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Quay 3.15 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Quay 3.16 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Quay 3.17 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Quay 3.9 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.4 CVSS 3.1 High 3.1 3.7 secalert@redhat.com via NIST National Vulnerability Database
7.4 CVSS 3.1 High 3.1 3.7 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database
7.4 CVSS 3.1 High — — redhat via CVE Program (cve.org) e CISA ADP
6.3 CVSS 3.1 Medium 2.8 3.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L (score shown at the top: secalert@redhat.com)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.4 (secalert@redhat.com via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-639 · Authorization Bypass Through User-Controlled Key (IDOR)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.43%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · red hat/mirror registry for red hat openshift 2.0, red hat/red hat quay 3.10, red hat/red hat quay 3.12, red hat/red hat
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.4
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Apr 8, 2026 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

11 on the record

Elsewhere on this site

Red Hat
every CVE for this vendor
Access control
same class
CWE-639
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-85471 Quay: quay: webhook notification ssrf -- hostname-string blocklist trivially bypassable 3d
  • CVE-2026-18255 Quay: quay: global read-only superuser can view robot account tokens Jul 29, 2026
  • CVE-2026-44495 Axios: Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge Jun 11, 2026
  • CVE-2026-6848 Quay: red hat quay: authentication bypass allows privileged actions without valid credentials Apr 22, 2026
  • CVE-2026-32591 Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration Apr 8, 2026
  • CVE-2026-32590 Mirror-registry: remote code execution using pickle deserialization Apr 8, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-32589 is "Mirror-registry: quay: insecure direct object reference in blobupload", rated High. It affects Mirror Registry For Red Hat Openshift (Red Hat); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.4 describes technical severity. EPSS 0.43% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.