Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-102295 Overview
CVE-2026-102295 is a reflected cross-site scripting (XSS) vulnerability in the OAuth callback handler of Red Hat Quay. The flaw stems from improper input sanitization [CWE-79] in the callback endpoint, allowing attacker-controlled data to render as executable JavaScript inside a victim's browser session. Exploitation requires a logged-in Quay user to click a crafted link. A successful attack executes arbitrary client-side script in the Quay application context, enabling session compromise, exposure of registry data, or unauthorized actions performed as the victim.
Critical Impact
An authenticated Quay user who visits a crafted OAuth callback URL can have their session hijacked and registry actions executed on their behalf.
Affected Products
- Red Hat Quay (container image registry)
- Deployments exposing the OAuth callback handler to end users
- Refer to the Red Hat CVE-2026-102295 Advisory for the authoritative list of affected versions
Discovery Timeline
- 2026-10-05 - CVE-2026-102295 published to the National Vulnerability Database (NVD)
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-102295
Vulnerability Analysis
The vulnerability resides in Quay's OAuth callback handler. The handler accepts parameters returned from an OAuth authorization flow and reflects at least one value into the HTTP response without proper encoding. An attacker who crafts a malicious callback URL can inject HTML or JavaScript that executes in the context of the Quay web application.
Because the injected code runs in the origin that hosts Quay, it has access to session cookies, CSRF tokens, and the authenticated API surface. The scope is limited to a single user session per click, but repeated phishing campaigns against Quay administrators can escalate the impact to registry-wide tampering.
The weakness is classified under CWE-79 (Improper Neutralization of Input During Web Page Generation). User interaction is required, which reduces exploitability relative to stored XSS but remains practical in targeted phishing scenarios.
Root Cause
The OAuth callback handler fails to encode or validate attacker-supplied input before writing it into the response body. Parameters such as state, error, or error_description returned by an identity provider flow are commonly reflected on error paths, and any of these can serve as the injection sink when sanitization is missing.
Attack Vector
An attacker crafts a URL pointing at the Quay OAuth callback endpoint and embeds a JavaScript payload in a reflected parameter. The attacker delivers the link through email, chat, or a malicious website. When a logged-in Quay user follows the link, the browser renders the response and executes the payload. The script can read session storage, call Quay APIs, exfiltrate registry tokens, or push, pull, and delete container images under the victim's identity.
See the Red Hat Bug Report #2542699 for additional technical context.
Detection Methods for CVE-2026-102295
Indicators of Compromise
- Requests to the Quay OAuth callback path containing HTML tags, javascript: schemes, or encoded <script> fragments in query parameters
- Outbound requests from a user browser to unfamiliar domains immediately after a Quay OAuth callback hit
- Unexpected OAuth token creation, repository permission changes, or image deletions performed by a user shortly after visiting an external link
Detection Strategies
- Inspect Quay access logs for callback requests containing suspicious characters such as <, >, %3C, %3E, or onerror=
- Alert on OAuth callback responses whose length or content-type deviates from the baseline for successful redirects
- Correlate web proxy telemetry with Quay authentication events to flag callbacks reached via external referrers
Monitoring Recommendations
- Forward Quay application and reverse-proxy logs into a centralized analytics platform for query across HTTP parameters and user agents
- Baseline normal OAuth callback traffic volume and parameter patterns, then alert on deviations
- Monitor privileged Quay accounts for anomalous API usage following any OAuth callback interaction
How to Mitigate CVE-2026-102295
Immediate Actions Required
- Apply the fixed Quay release referenced in the Red Hat CVE-2026-102295 Advisory as soon as it is available for your deployment channel
- Invalidate existing user sessions and rotate OAuth client secrets after patching to contain any prior exploitation
- Review Quay audit logs for unexpected OAuth application registrations, token issuance, or repository permission changes
Patch Information
Red Hat tracks remediation guidance and fixed component versions in the Red Hat CVE-2026-102295 Advisory and Red Hat Bug Report #2542699. Deploy the vendor-supplied update that introduces output encoding on the OAuth callback handler.
Workarounds
- Place a web application firewall (WAF) in front of Quay and block requests to the OAuth callback path that contain HTML or script metacharacters in query parameters
- Enforce a strict Content Security Policy (CSP) that disallows inline scripts and restricts script sources to trusted origins
- Instruct Quay users to avoid clicking OAuth or registry links from untrusted sources until the patch is applied
# Example NGINX rule to block script-like payloads in Quay OAuth callback query strings
location ~* ^/oauth2/.*/callback {
if ($args ~* "(<|%3C)\s*script|javascript:|onerror=|onload=") {
return 400;
}
proxy_pass http://quay_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

