# CVE-2026-102295: Quay: quay: dom-based cross-site scripting via oauth local callback format=json parameter

> A remote attacker can execute arbitrary JavaScript in a logged-in user's browser via a crafted OAuth callback link, potentially compromising sessions and accessing sensitive registry data.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/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-fjvc-v8v8-pmj9

## What is CVE-2026-102295?

CVE-2026-102295 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 cross-site scripting (XSS) vulnerability in the OAuth callback handler allows a remote attacker to execute arbitrary JavaScript code within a user's browser session. By tricking a logged-in user into visiting a specially crafted link, an attacker can exploit improper input sanitization to run client-side scripts in the application context. Successful exploitation could allow the attacker to compromise the user's session, access sensitive registry information, or perform unauthorized actions on their behalf.

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

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


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

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

## Is CVE-2026-102295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102295 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-102295 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-102295/ (Markdown: https://insights.sbomify.com/CVE-2026-102295/index.md)
```

## Sources

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

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