Description
A flaw was found in Red Hat Quay. The build trigger management application programming interface (API) fails to verify whether a requested trigger belongs to the specified repository. An authenticated user with administrative access to any repository can view, modify, or permanently delete build triggers and associated write tokens of another repository if they know the victim trigger's universally unique identifier (UUID).
Published: 2026-10-12
Score: 6.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized access to build triggers and tokens
Action: Mitigate Access Controls
AI Analysis

Impact

A flaw in the Red Hat Quay 3 API allows an authenticated administrator to retrieve, modify, or delete build triggers of another repository by providing the trigger’s UUID. The vulnerability stems from a missing ownership check, enabling an IDOR that exposes the associated write tokens and confers full manipulation rights over the victim repository. This effectively grants the attacker control over the victim repository’s build triggers and tokens.

Affected Systems

The issue affects Red Hat Quay version 3, which is deployed by Red Hat as part of the Quay Container Registry solution.

Risk and Exploitability

The CVSS score of 6.4 indicates moderate severity. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, suggesting it is not widely exploited yet. Nonetheless, the flaw requires authenticated administrative privileges and could be abused by anyone who gains repository‑level admin access. The attack vector is the Quay API; the vulnerability does not require network compromise or local execution, so the impact is confined to repositories controlled by the attacker.

Generated by OpenCVE AI on October 12, 2026 at 17:28 UTC.

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

  • Limit API access for administrative users to a trusted network segment and enforce least‑privilege on repository‑administrator accounts.
  • Review current repository administrators and remove those who no longer require full‑access rights; log all changes to detect unauthorized modifications.
  • Verify that API endpoints properly enforce repository ownership checks so that only authorized administrators can access triggers and associated tokens.

Generated by OpenCVE AI on October 12, 2026 at 17:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 25 Oct 2026 17:15:00 +0000

Type Values Removed Values Added
First Time appeared Red Hat
Red Hat red Hat Quay 3
Redhat red Hat Quay 3
Vendors & Products Red Hat
Red Hat red Hat Quay 3
Redhat red Hat Quay 3

Tue, 13 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Tue, 13 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 12 Oct 2026 15:45:00 +0000

Type Values Removed Values Added
Description A flaw was found in Red Hat Quay. The build trigger management application programming interface (API) fails to verify whether a requested trigger belongs to the specified repository. An authenticated user with administrative access to any repository can view, modify, or permanently delete build triggers and associated write tokens of another repository if they know the victim trigger's universally unique identifier (UUID).
Title Quay: build trigger 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': 6.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L'}


Subscriptions

Red Hat Red Hat Quay 3
Redhat Quay Red Hat Quay 3
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-10-13T15:25:21.637Z

Reserved: 2026-10-12T13:19:27.534Z

Link: CVE-2026-109194

cve-icon Vulnrichment

Updated: 2026-10-13T15:25:10.389Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-12T16:17:04.090

Modified: 2026-10-15T16:33:26.290

Link: CVE-2026-109194

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-12T00:00:00Z

Links: CVE-2026-109194 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-25T17:15:15Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key