# CVE-2026-109194: Quay: build trigger uuid idor in quay api

> An authenticated user with admin access to any repository can view, modify, or delete build triggers and write tokens of other repositories via IDOR.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-rfw7-pm7r-4ppw

## What is CVE-2026-109194?

CVE-2026-109194 is a medium-severity missing authorization vulnerability in Red Hat Quay 3, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-109194?


## How do I fix CVE-2026-109194?

No fix has been published for CVE-2026-109194 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109194 being exploited?

There is no known exploitation of CVE-2026-109194 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109194 and fix it if it is affected.

What it is: CVE-2026-109194 is a medium-severity missing authorization vulnerability in Red Hat Quay 3, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109194 in the wild and no public exploit code.

Affected product: Red Hat Quay 3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109194/ (Markdown: https://insights.sbomify.com/CVE-2026-109194/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109194
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109194
- OSV: https://osv.dev/vulnerability/CVE-2026-109194

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109194/
Summaries are generated and may contain mistakes; the official description above is the record.