CVE-2026-74245

A flaw was found in Red Hat Quay where the build trigger management API fails to verify whether a requested trigger belongs to the specified repository.

In Red Hat Quay, a user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit an SSRF vulnerability within the build API by providing a malicious URL, causing the builder to make requests to internal network addresses.

In Red Hat Quay's Stripe billing webhook handler, an unauthenticated attacker can forge billing events by sending crafted JSON requests to the /webhooks/stripe endpoint without validating the Stripe-Signature header.

In Red Hat Quay, when SECURITY_SCANNER_V4_PSK is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint, allowing flooding of the notification queue and injection of path traversal characters into Clair API URL paths.

In Red Hat Quay, an administrator of any repository, by knowing or guessing a target notification's UUID, can read the notification configuration, including sensitive details like webhook URLs, Slack tokens, and email addresses. They can also trigger test notifications for another repository.

In Red Hat Quay's external LDAP authentication handling, when an LDAP referral is returned during authentication, the system does not properly escape the username input. This allows an attacker to inject LDAP filter metacharacters, enabling user-existence oracle attacks at the referral DN.

In Red Hat Quay's JWT validation for federated robot accounts and SSO authentication, multiple issues related to audience verification and enforcement of azp and sub claims were identified. An attacker with a validly-signed token from the same identity provider could bypass configured security restrictions.

In Red Hat Quay, the Slack and generic webhook notification handlers do not validate URLs against SSRF. A repository administrator can force the Quay worker to send POST requests to internal network addresses or cloud endpoints.

SSRF vulnerability in Red Hat Quay's repository-level mirror configuration. A repository administrator can supply a crafted hostname causing the Quay mirror worker to make requests to internal network services.

In Red Hat Quay, the proxy cache configuration feature does not verify that the specified upstream registry hostname points to a legitimate external service. An organization administrator can supply a crafted hostname, forcing the Quay server to make requests to internal network services, cloud infrastructure endpoints, or other resources that should not be accessible from the Quay application.