CVE-2026-102576: Quay: quay: dom-based cross-site scripting via unvalidated redirect_url on signin page

Published Sep 29, 2026
·
Updated

A DOM-based cross-site scripting flaw was found in Project Quay's signin page (Signin.tsx). After a user completes a successful direct database login, the component reads the redirecturl query parameter and assigns it to window.location.href without validating the URL scheme or origin. An attacker can set redirecturl to a javascript: URI, causing arbitrary JavaScript execution in the authenticated Quay session after login. Exploitation requires the target deployment to use database authentication and the user to successfully authenticate through the crafted URL.

Other sources

A flaw was found in Quay. A remote attacker could trick a user into logging in through a crafted link, resulting in cross-site scripting (XSS). Because the application does not validate the redirect destination before navigating, this flaw allows the execution of arbitrary script in the context of the victim's authenticated browser session. Successful exploitation requires the target Quay deployment to use direct database authentication and the victim to complete login through the malicious URL.

— MITRE

Affected Software

1 affected component
Red Hat Quay

Event History

Sep 29, 2026
Data Sourced
via Red Hat·01:58 PM
DescriptionSeverityAffected Software
Oct 5, 2026
CVE Published
via MITRE·05:02 PM
Data Sourced
via MITRE·05:02 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using direct database authentication are exposed. Exploitation depends on a user successfully completing a database login through an attacker-crafted signin URL.

2

What must an attacker do to exploit the flaw?

The attacker must convince a user to open a crafted signin link containing a redirect_url parameter set to a javascript: URI. The user must then successfully authenticate, after which script executes in that user's authenticated Quay browser session.

3

Is user interaction required?

Yes. The victim must be tricked into using the crafted link and must complete the login process; the issue does not execute solely from an unauthenticated remote request.

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