CVE-2026-74242: Quay: repository notification uuid idor in quay api

Published Aug 14, 2026
·
Updated

A flaw was found in Red Hat Quay. An administrator of any repository, by knowing or guessing a target notification's Universally Unique Identifier (UUID), can read the notification configuration, including sensitive details like webhook URLs, Slack tokens, and email addresses. This vulnerability also allows them to trigger test notifications for another repository. This could lead to unauthorized information disclosure and potential misuse of notification services.

Other sources

A flaw was found in Red Hat Quay's repository notification API endpoints. The GET and test-trigger endpoints in endpoints/api/repositorynotification.py look up notifications by UUID without verifying that the notification belongs to the repository specified in the URL path. An admin of any repository who knows or guesses a target notification's UUID can read the notification configuration (including webhook URLs, Slack tokens, and email addresses) and fire test notifications for another repository's notification. The DELETE and reset endpoints correctly scope by repository. Exploitation requires knowing a 128-bit notification UUID.

Red Hat

Affected Software

1 affected component
Red Hat Quay

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Restrict access to Quay repository notification API endpoints (endpoints/api/repositorynotification.py) so only authorized administrators for a given repository can call the GET and test-trigger operations that use a repository path plus a notification UUID.

Event History

Aug 14, 2026
Data Sourced
via Red Hat·07:50 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·10:43 PM
Data Sourced
via MITRE·10:43 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-74242?

CVE-2026-74242 has a medium severity rating of 5.3.

2

How do I fix CVE-2026-74242?

To mitigate CVE-2026-74242, ensure that access controls are correctly implemented and restrict knowledge of repository notification UUIDs.

3

What type of vulnerability is CVE-2026-74242?

CVE-2026-74242 is an IDOR (Insecure Direct Object Reference) vulnerability.

4

What products are affected by CVE-2026-74242?

CVE-2026-74242 affects Red Hat Quay.

5

What can an attacker do with CVE-2026-74242?

An attacker can read sensitive notification configurations by guessing the UUID of the notifications.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203