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

> Attackers can execute arbitrary scripts in victim sessions via unvalidated redirects on the Quay sign-in page, requiring direct database authentication.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-f2m3-wc4v-9hhm

## What is CVE-2026-102576?

CVE-2026-102576 is a medium-severity cross-site scripting vulnerability in Red Hat Quay 3, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-102576?


## How do I fix CVE-2026-102576?

No fix has been published for CVE-2026-102576 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102576 being exploited?

There is no known exploitation of CVE-2026-102576 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102576 and fix it if it is affected.

What it is: CVE-2026-102576 is a medium-severity cross-site scripting vulnerability in Red Hat Quay 3, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102576 in the wild and no public exploit code.

Affected product: Red Hat Quay 3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102576/ (Markdown: https://insights.sbomify.com/CVE-2026-102576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102576
- OSV: https://osv.dev/vulnerability/CVE-2026-102576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102576/
Summaries are generated and may contain mistakes; the official description above is the record.