LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw lets a logged-in user who can push to any repository interfere with another user’s container image upload, even in repositories they cannot access. The business risk is supply-chain disruption or tampering during image publishing, especially in shared Red Hat Quay or mirror registry environments.

Executive priority

Treat as high priority for shared registries supporting production image pipelines. The issue can undermine image publishing integrity and availability, but the sources do not support internet-wide unauthenticated exploitation or confirmed active exploitation.

Technical view

CVE-2026-32589 is a CWE-639 insecure direct object reference in Red Hat Quay blobupload handling. An authenticated low-privilege pusher can access another in-progress upload object across repository boundaries, potentially reading, modifying, or canceling that upload. CVSS 3.1 score is 7.4 high.

Likely exposure

Exposure is likely where affected Red Hat Quay 3.9 through 3.17 or mirror registry for Red Hat OpenShift instances allow multiple users or teams to push images. Single-tenant or tightly controlled registries have lower practical exposure.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires authentication and push access to some repository, but not to the victim repository. The impact is limited to uploads in progress, not completed images per the sources.

Researcher notes

Focus validation on authorization boundaries in blobupload lifecycle handling. Evidence supports cross-repository interference by authenticated push users. The source bundle does not provide proof-of-concept details, fixed package versions, or runtime indicators beyond vendor advisories and affected package streams.

Mitigation direction

  • Identify affected Red Hat Quay and mirror registry deployments listed in the Red Hat CVE data.
  • Review the matching Red Hat RHSA advisory for the deployed product and version.
  • Apply vendor-provided updates or mitigations only as directed by Red Hat guidance.
  • Restrict push access to trusted users until remediation is complete.
  • Monitor registry upload failures, cancellations, and unexpected image changes.

Validation and detection

  • Inventory Quay and mirror registry package versions against the affected product list.
  • Confirm whether untrusted or cross-team users have push access to any repository.
  • Check Red Hat advisory applicability for each deployed version and package stream.
  • Review audit logs for unusual upload cancellation, overwrite, or cross-repository access patterns.
  • After remediation, verify deployed package versions match Red Hat guidance.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32589 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
7Timeline events
2ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L3.13.7redhat
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L3.13.7redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2026-32589Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Reported to Red Hat.

  3. Source timelineredhat

    Reported to Red Hat.

  4. ADP timelineredhat-SADP

    Made public.

  5. Source timelineredhat

    Made public.

  6. CVE publishedCVE Program

    The CVE record was published.

  7. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPmirror-registry: quay: insecure direct object reference in BlobUpload
other:Red Hat severity ratingcvssV3_1
  • 2026-03-12T14:43:07.878Z: Reported to Red Hat.
  • 2026-04-08T00:00:00.000Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red Hatmirror registry for Red Hat OpenShift 2.0openshift/mirror-registry-rhel8, 1782177012affected
Red HatRed Hat Quay 3.10quay/quay-rhel8, 1779822261affected
Red HatRed Hat Quay 3.12quay/quay-rhel8, 1779811412affected
Red HatRed Hat Quay 3.14quay/quay-rhel8, 1779689392affected
Red HatRed Hat Quay 3.15quay/quay-rhel8, 1780891395affected
Red HatRed Hat Quay 3.16quay/quay-rhel9, 1779204086affected
Red HatRed Hat Quay 3.17quay/quay-rhel9, 1779922205affected
Red HatRed Hat Quay 3.9quay/quay-rhel8, 1779811473affected
Red Hatmirror registry for Red Hat OpenShiftopenshift/mirror-registry-rhel8affected
Weakness

CWE details

CWE-639

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs