CVE-2026-109195

Quay: repository auto-prune policy uuid idor in quay api

Published Oct 12, 2026 CVSS 3.1 · 3.1 Low EPSS < 1% KEV · Not listed
Description
A flaw was found in Quay. An authenticated attacker can access repository auto-prune configurations from other namespaces, leading to unauthorized information disclosure. This issue occurs because the application does not properly enforce namespace scoping when retrieving policy details by repository name and policy identifier. To exploit the vulnerability, the attacker must manage a repository sharing the target's name and know the target policy's unique identifier.

Analysis

AI-generated

Technical impact

This vulnerability allows an authenticated user to read auto‑prune policy information for repositories in other namespaces, resulting in unauthorized information disclosure. Because the system does not enforce namespace scoping when a policy is requested by name and identifier, an attacker who controls a repository sharing a target name and knows the target policy UUID can retrieve that data. The weakness is an authorization bypass (CWE‑639).

Affected Systems

The flaw affects Red Hat Quay 3 deployments. Any instance of Red Hat Quay 3 that permits user authentication with repository management privileges could be impacted. No specific version range is listed; the vulnerability applies to all Red Hat Quay 3 releases until a fix is released.

Risk and Exploitability

The CVSS score of 3.1 indicates low severity, and EPSS is not available, so the likelihood of exploitation is not quantified. The issue is not listed in CISA KEV. The attack requires the attacker to be authenticated to Quay, have control of a repository that shares the same name as the target repository, and know the target policy UUID. Because the attacker must already possess a valid account with repository permissions, exploitation is limited to insiders or compromised accounts. No public exploit code is available; however, the conditions for exploitation are straightforward for a privileged user, making the risk affect confidentiality in the affected instance.

Remediation

Vendor Workaround

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.


OpenCVE Recommended Actions

  • Ensure that repository names are unique across namespaces or implement strict namespace-checking in your Quay deployment.
  • Restrict user privileges so that only trusted users can create or manage repositories that share names with other namespaces.
  • Monitor API calls for auto‑prune policy retrieval and audit logs for unauthorized access attempts.
  • Contact Red Hat for a patch update once released, and apply it immediately.
  • No effective workaround is available; Red Hat notes that existing options do not meet security criteria.

Generated by OpenCVE AI on October 12, 2026 at 16:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Red Hat
Red Hat red Hat Quay 3
Vendors & Products Red Hat
Red Hat red Hat Quay 3
Type Values Removed Values Added
Description A flaw was found in Quay. An authenticated attacker can access repository auto-prune configurations from other namespaces, leading to unauthorized information disclosure. This issue occurs because the application does not properly enforce namespace scoping when retrieving policy details by repository name and policy identifier. To exploit the vulnerability, the attacker must manage a repository sharing the target's name and know the target policy's unique identifier.
Title Quay: repository auto-prune policy uuid idor in quay api
First Time appeared Redhat
Redhat quay
Weaknesses CWE-639
CPEs cpe:/a:redhat:quay:3
Vendors & Products Redhat
Redhat quay
References
Metrics cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Oct 14, 2026, 3:33 PM
Reserved
Oct 12, 2026, 1:19 PM
Status
Awaiting Analysis
Published
Oct 12, 2026, 4:17 PM
Modified
Oct 15, 2026, 4:33 PM
Severity
Low
Public date
Oct 12, 2026, 12:00 AM