CVE-2026-109194 Red Hat CVE debrief

Who should care

Defenders responsible for Red Hat Quay 3 deployments should assess exposure and prioritize verifying and restricting access to build triggers and associated write tokens. This includes reviewing compensating controls, monitoring for suspicious activity, and implementing additional security measures to prevent unauthorized access to repositories. Security teams should also track exceptions, retest remediated assets, and close the item only after evidence is

Why it matters

CVE-2026-109194 is a vulnerability in Red Hat Quay 3 that allows an authenticated user with administrative access to any repository to 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). Defenders should prioritize verifying and restricting access to build triggers and associated write tokens in Red Hat Quay 3.

• Potential unauthorized access to repositories
• Possible modification or deletion of build triggers and write tokens
• Required verification of build trigger and write token access controls
• Need for monitoring suspicious activity related to build triggers and write tokens

Technical summary

The build trigger management API in Red Hat Quay 3 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). This vulnerability allows unauthorized access to build triggers and write tokens, potentially leading to repository compromise. The vulnerability is based on the CVE Program record and the NVD vulnerability detail page.

Defensive priority

Defenders should prioritize verifying and restricting access to build triggers and associated write tokens in Red Hat Quay 3.

Recommended defensive actions

• Verify and restrict access to build triggers and associated write tokens in Red Hat Quay 3
• Monitor for suspicious activity related to build triggers and write tokens
• Implement additional security measures to prevent unauthorized access to repositories
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is described in the CVE Program record and the NVD vulnerability detail page. The source item provides additional information about the vulnerability. Evidence limits are based on available information from these sources. Defenders should verify build trigger and write token access controls, monitor for suspicious activity, and implement additional security measures to prevent unauthorized access to repositories. No exploit details are publicly available, but the vulnerability's impact on repository security is a key

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.