dbcve.org
Mirror Registry For Red Hat OpenshiftApplication · Redhat

CVE-2026-32589

HIGH · 7.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Red Hat Quay lacks proper authorization checks on in-progress image upload sessions. Authenticated users with push access to any repository can access, modify, or cancel other users' upload sessions, including those in repositories they don't have access to. This allows cross-user and cross-repository upload interference due to insufficient validation of session ownership and repository access rights during the upload process.

MitigationImplement proper session ownership verification and repository access control checks before allowing any read, modification, or cancellation operations on in-progress uploads. Ensure upload sessions can only be accessed by the user who initiated them and only for repositories where that user has appropriate permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mirror Registry For Red Hat OpenshiftApplication
Affected:all versions= 2.0
QuayApplication
Affected:= 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Quay version
    Check the version of Red Hat Quay or Mirror Registry by querying the API endpoint /api/v1/version or checking the container image tags
    Affected if The installed version matches 3.0.0 (Quay) or is any version of Mirror Registry (2.0)
  2. Verify image repository push access is enabled
    Confirm that users have the ability to push images to repositories - check repository permissions and the presence of push functionality in the Quay configuration
    Affected if Repository push access is enabled for authenticated users, creating the condition for the vulnerability to be exploited
  3. Confirm multi-user environment with repository isolation
    Check if multiple users exist with push access to different repositories, and verify repository-level access controls are in place
    Affected if Multiple users have push access to different repositories with the expectation of isolation between them
  4. Test upload session endpoint access controls
    Using an authenticated account with push access to one repository, attempt to access or manipulate an upload session identifier from a different user's session (checking if unauthorized access is possible)
    Affected if A user can read, modify, or cancel upload sessions belonging to other users for repositories they do not have access to

A user is affected if they are running the specified versions and have multiple users with push access to different repositories, where one user can access another user's upload session identifiers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper session ownership verification and repository access control checks before allowing any read, modification, or cancellation operations on in-progress uploads. Ensure upload sessions can only be accessed by the user who initiated them and only for repositories where that user has appropriate permissions.

Fix this in Mirror Registry For Red Hat Openshift Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32589 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data