# CVE-2026-102295: Red Hat Quay XSS in OAuth callback handler

Source: https://junglewise.ai/threats/cve-2026-102295-a-flaw-was-found-in-quay-a-cross-site-scripting-xss  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-05. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-102295 · Severity: medium · CVSS 5.4 · Published 2026-10-05

Red Hat Quay is a container image registry that stores and manages Docker images for organizations. A cross-site scripting (XSS) vulnerability in its OAuth login callback handler allows an attacker to trick logged-in users into visiting a malicious link that executes arbitrary JavaScript in their browser. Successful exploitation could lead to session hijacking, theft of sensitive registry data, or unauthorized actions performed on behalf of the victim user.

Technologies: [Red Hat Quay](https://junglewise.ai/threats/technologies/quay-3-12). Vendors: [Red Hat](https://junglewise.ai/threats/vendors/red-hat).

## Quick answers

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

**How severe is CVE-2026-102295?** Medium severity, with a CVSS score of 5.4, published 5 October 2026.

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

**Is there a fix for CVE-2026-102295?** 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-102295 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-102295?** Check whether you run Red Hat Quay at an affected version. 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

A DOM-based XSS flaw exists in Quay's OAuth local callback handler, introduced in the React-based OAuth implementation in version 3.16. The vulnerability stems from improper input sanitization in a non-default code path triggered by the format=json parameter. Exploitation requires user interaction (clicking a crafted link) but no privileges; the attacker gains execution context within the victim's authenticated browser session.

## Affected products

- Red Hat Quay 3.16 and later

## Timeline

- 2026-10-05: 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-102295](https://access.redhat.com/security/cve/CVE-2026-102295)

## Related threats

- [Red Hat Quay SQL injection in robot account listing](https://junglewise.ai/threats/cve-2026-110697-a-flaw-was-found-in-quay-where-the-robot-account-listing)
- [Red Hat Quay unauthenticated service key takeover](https://junglewise.ai/threats/cve-2026-123710-a-flaw-was-found-in-red-hat-quay-an-unauthenticated-client-can)
- [Quay webhook hostname blacklist bypass leading to SSRF](https://junglewise.ai/threats/cve-2026-85471-a-flaw-was-found-in-quay-an-authenticated-repository)
- [Red Hat Quay build trigger API authorization bypass](https://junglewise.ai/threats/cve-2026-109194-a-flaw-was-found-in-red-hat-quay-the-build-trigger-management)
- [Red Hat Quay privilege escalation in build trigger API](https://junglewise.ai/threats/cve-2026-105447-a-flaw-was-found-in-quay-when-handling-build-trigger-requests)