Back to the CVE list
CVE-2026-109194

Quay: build trigger uuid idor in quay api

CVSS score

6.4

EPSS probability

—

Risk score

0.6

Published

11 h ago

OverviewPublic Exploits (0)NewsroomVulnerability Timeline
Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

CVE AI research

The stored explanation is shown at once; refreshing evaluates the sources again.

DayBreach AI Explanation

Verified against sources

Red Hat Quay IDOR Vulnerability (CVE-2026-109194)

Sources read

2

Source agreement

Tam uyum

Evidence confidence

%63

Short explanation

An IDOR flaw exists in Red Hat Quay 3 within the build trigger management API. The flaw requires the attacker to know the target trigger UUID.

Why does it matter?

An authenticated user with administrative access to any repository can impact build triggers and associated write tokens of another repository.

What should be done?

  • Follow official vendor advisories.
  • Review repository authorization controls.
  • Monitor API access.
Chain of evidence and sources2 verified claims

Red Hat Quay 3 yapı tetikleyici yönetim API'si, tetikleyicinin depoya ait olduğunu doğrulamaz.

S0 · daybreach-canonicalS1 · cvelistS2 · nvd

Yetkili kullanıcılar hedef tetikleyicinin UUID değerini bilerek diğer depoları etkileyebilir.

S0 · daybreach-canonicalS1 · cvelistS2 · nvd
Show the technical text from the sources

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).

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

CWE: CWE-639

Explanation produced with the local gemini-flash-lite-latest model. Numerical metrics and the KEV, patch and exploit statuses are not determined by AI.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-109194 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1Red HatRed Hat Quay 3 View
Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
6.4CVSS V31MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:LNVD
6.4CVSS V3_1MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:LCVE CNA

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-109194 is associated with the following CWEs:

CWE-639: Common Weakness Enumeration Entry CWE-639

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-109194 weaknesses.

CAPEC-66: SQL InjectionCAPEC-126: Path TraversalCAPEC-28: OS Command Injection

Attack Vector and Accessibility

ExposureAğ üzerinden
PermissionsLow
UserGerekmiyor

Official Sources and Advisories

https://access.redhat.com/security/cve/CVE-2026-109194vendor-advisoryRHBZ#2549645vendor-advisory

CVSS Vector Radar Chart

6.4 / 10
Attack VectorNetworkComplexityHighPrivilegesLowUser Interact.NoneConfidentialityHighIntegrityNoneAvailabilityLow

Vulnerability Scoring Details

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow privileges
User InteractionNone required
Confidentiality (Gizlilik)High
Integrity (Bütünlük)None
Availability (Erişilebilirlik)Low

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

RH
Red Hat logo
Red Hat

Weakness Type (CWE & CAPEC)

CWE-639

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

Get a free keyDocumentation
curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.enginteksut.com.tr/api/v1/intel/cves/CVE-2026-109194"
CVE-2026-109194 · Quay: build trigger uuid idor in quay api · DayBreach