Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPhish authenticated Quay user with crafted link
-
DeliveryVictim clicks link to OAuth callback
-
ExploitUnsanitized parameter reflected into page
-
ExecutionInjected JavaScript executes in app context
-
ImpactHijack session and act as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to be an authenticated Quay user with an active session who is lured into clicking an attacker-crafted URL that triggers Quay's OAuth callback handler; the injected script then executes because the callback performs improper input sanitization. Limiting factors: mandatory user interaction (UI:R), the victim must already be logged in for session/registry impact, and the attacker must deliver the malicious link (e.g., via phishing). Impact is confined to the victim's browser session in the Quay application context rather than server-side compromise. |
| Impact | This is a moderate-severity reflected/DOM XSS (CWE-79) in Red Hat Quay 3's OAuth callback handler, scored CVSS 5.4 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N). The network vector and low attack complexity favor the attacker, but exploitation is gated by UI:R - a logged-in victim must be tricked into clicking a crafted link - and the impact is bounded to Low confidentiality and Low integrity with no availability effect, consistent with session/token theft and actions in the victim's context rather than full registry compromise. No EPSS score, CISA KEV listing, POC, or SSVC decision data were supplied, so there is no evidence of active exploitation or published exploit code; this appears to be a genuine but not emergency-priority issue. The absence of exploitation-probability signals means prioritization should rest on CVSS and exposure: patch during normal cadence, prioritizing internet-facing Quay instances. No conflicts between the CVSS vector and the description were observed - both agree on remote, user-interaction-dependent, limited-impact client-side execution. |
| Exploit ScenarioDerived | An attacker crafts a malicious link targeting Quay's OAuth callback endpoint with an unsanitized parameter and sends it to an authenticated Quay user (e.g., via phishing). When the logged-in victim opens the link, injected JavaScript runs in the Quay application context, letting the attacker steal the session/OAuth token, read sensitive registry data, or perform actions as the victim. No public exploit code was identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Cross-site scripting in the OAuth callback handler of Red Hat Quay 3 lets an unauthenticated remote attacker run arbitrary JavaScript in a logged-in user's browser session by luring that user to a crafted URL, with no attacker privileges required (PR:N) but mandatory victim interaction (UI:R), giving a CVSS 3.1 score of 5.4. Successful exploitation is scoped to the victim's Quay application session (S:U, low confidentiality and integrity impact, no availability impact), potentially exposing registry metadata or allowing actions to be performed as the victim, rather than yielding server-side compromise. The vulnerability class is CWE-79 improper neutralization of input during web page generation; no public exploit code was identified in the available intelligence at the time of analysis, and CISA KEV status was not indicated.
RemediationAI
No vendor-released patch version is identified in the provided data; Red Hat advisories at https://access.redhat.com/security/cve/CVE-2026-102295 and https://bugzilla.redhat.com/show_bug.cgi?id=2542699 should be monitored for the fixed Quay 3 release and administrators should upgrade to that version as soon as it is published, since the absence of a version number in this feed is not confirmation that no fix exists. In the interim, deploy a Content-Security-Policy on the Quay web front end that disallows inline and third-party script (for example script-src 'self' without 'unsafe-inline'), accepting the trade-off that Quay UI components relying on inline script may break and require policy tuning; strip or strictly encode untrusted query-string values reaching the OAuth callback endpoint at a reverse proxy so that script payloads are neutralized before rendering, with the caveat that overly aggressive filtering can disrupt legitimate OAuth redirects and must be tested against normal login flows. Set Quay session cookies with HttpOnly, Secure, and SameSite=Lax or Strict to limit token theft through injected script, though note this does not prevent in-context actions performed as the victim, and add WAF or proxy rules that block script-like payloads in callback parameters as a detection and containment layer. Because exploitation depends on social engineering, reinforce user awareness around unsolicited Quay links and require re-authentication or session invalidation for users suspected of having clicked a crafted callback URL; blocking the callback endpoint outright is not a viable control because it would break OAuth-based logins.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a cross-site scripting (CWE-79) defect in the OAuth callback handler of Red Hat Quay 3, an open-source container image registry commonly deployed as Red Hat Quay. OAuth 2.0 authorization-code flows rely on a redirect/callback endpoint that receives attacker-influenceable query parameters (such as authorization codes, state values, error descriptions, or redirect targets) and renders them back to the user's browser; the callback here performs improper input sanitization, so crafted parameter content is emitted into the page context and executed as client-side script. The provided CPE cpe:2.3:a:red_hat:red_hat_quay_3:*:*:*:*:*:*:*:* identifies Red Hat Quay 3 as the affected product line with no version restriction recorded in the feed. Because execution occurs in the origin of the Quay web application, injected script inherits the victim's authenticated session context, meaning it could read registry information rendered in the page or issue authenticated requests as the victim. The assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N confirms network reachability, low attack complexity, no required attacker privileges, mandatory user interaction, unchanged scope, and limited confidentiality/integrity impact with no availability impact, consistent with a moderate-severity reflected/DOM-style XSS rather than a server-side takeover.
Know when Red Hat Quay 3 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Remote attacker needs no privileges (PR:N) but a logged-in victim must click a crafted link (UI:R); reflected XSS yields limited session/data impact (C:L/I:L), no availability effect.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Affected Products (CPE)CVE.org
More in Red Hat Quay 3
View allThe system CA trust store shipped in Red Hat's ca-certificates RPM packages includes eMudhra root authorities that signe
Authenticated remote code execution in Red Hat Quay 3 and Mirror Registry for Red Hat OpenShift arises from unsafe deser
Red Hat Quay 3 and Red Hat OpenShift Update Service expose an unauthenticated security scanner notification endpoint whe
Red Hat Quay 3 bypasses password re-verification for sensitive operations such as token generation and robot account cre
Red Hat Quay 3's exported action logs download endpoint fails to enforce authorization, permitting any network-accessibl
Red Hat Quay's Stripe billing webhook handler at /webhooks/stripe processes inbound JSON payloads without verifying the
Red Hat Quay's container image upload mechanism allows authenticated users with push privileges to interfere with concur
Robot account token disclosure in Red Hat Quay 3 allows a user assigned to the GLOBAL_READONLY_SUPER_USERS role to read
Server-Side Request Forgery in Red Hat Quay's build API allows an authenticated user with repository write access to piv
Server-Side Request Forgery in Red Hat Quay 3 and Mirror Registry for Red Hat OpenShift 2 allows an authenticated reposi
LDAP injection in Red Hat Quay 3's external LDAP authentication handler allows unauthenticated network attackers to inje
Server-side request forgery (SSRF) in Red Hat Mirror Registry and Red Hat Quay 3.x allows authenticated users to conduct
EUVD-2026-92518
GHSA-fjvc-v8v8-pmj9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB