# CVE-2026-74242: Red Hat Quay notification UUID authorization bypass

Source: https://junglewise.ai/threats/cve-2026-74242-red-hat-quay-notification-uuid-authorization-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-14. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-74242 · Severity: medium · CVSS 5.3 · Published 2026-08-14

Red Hat Quay is a container image registry platform used by enterprises to store and manage containerized applications. A vulnerability allows authenticated repository administrators to access notification configurations of other repositories by guessing a notification's unique identifier, exposing sensitive data like webhook URLs and authentication tokens. This could enable attackers to discover credentials or interfere with notification systems across the platform.

Technologies: [Redhat Quay](https://junglewise.ai/threats/technologies/quay). Vendors: [Redhat](https://junglewise.ai/threats/vendors/redhat).

## Quick answers

**Is CVE-2026-74242 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-74242 being exploited in the wild.

**How severe is CVE-2026-74242?** Medium severity, with a CVSS score of 5.3, published 14 August 2026.

**Which products and versions are affected?** Red Hat Quay.

**Is there a fix for CVE-2026-74242?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-74242 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-74242?** Check whether you run Redhat Quay. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

This is an insecure direct object reference (IDOR) vulnerability in Red Hat Quay's notification API. An authenticated repository administrator can read notification configurations of any repository by knowing or guessing a 128-bit notification UUID, bypassing authorization checks. The vulnerability also permits triggering test notifications for other repositories. The attack requires network access and valid repository admin credentials, but the 128-bit UUID space and lack of rate limiting make enumeration feasible. Red Hat rates this as Moderate impact due to the authentication requirement and UUID guessing complexity, though successful exploitation exposes sensitive webhook URLs, Slack tokens, and email addresses. No mitigation is currently available beyond upgrading to a patched version.

## Affected products

- Red Hat Quay

## Timeline

- 2026-08-14: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-74242](https://access.redhat.com/security/cve/CVE-2026-74242)

## Related threats

- [Red Hat Quay Server-Side Request Forgery in build API](https://junglewise.ai/threats/cve-2026-74247-red-hat-quay-server-side-request-forgery-in-build-api)
- [Red Hat Quay authentication bypass in exported logs](https://junglewise.ai/threats/cve-2026-74245-red-hat-quay-authentication-bypass-in-exported-logs)
- [Red Hat Quay Stripe webhook signature validation bypass](https://junglewise.ai/threats/cve-2026-74244-red-hat-quay-stripe-webhook-signature-validation-bypass)
- [Red Hat Quay authentication bypass in security scanner notification endpoint](https://junglewise.ai/threats/cve-2026-74243-red-hat-quay-authentication-bypass-in-security-scanner)
- [Red Hat Quay LDAP injection in external authentication](https://junglewise.ai/threats/cve-2026-74241-red-hat-quay-ldap-injection-in-external-authentication)