Quay. A cross-site scripting (XSS) vulnerability · Cross-site Scripting
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 18 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.4 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Quay 3quay/quay-rhel9 | Affected– | Fixed in– |
AI-suggested
Users should be aware of the risk of clicking untrusted links and monitor Red Hat advisories for future updates or patches. Consider restricting access to the OAuth callback handler or implementing custom input sanitization if feasible until an official fix is released.
Description
A DOM-based cross-site scripting (XSS) vulnerability exists in Quay's OAuth callback handler. This flaw allows a remote attacker to execute arbitrary JavaScript in the browser session of a logged-in user by tricking them into visiting a specially crafted URL. Exploitation requires user interaction and targets a non-default code path involving the format=json parameter. The vulnerability was introduced in Quay version 3.16 with the React-based OAuth handler. No official fix or mitigation meeting Red Hat's criteria is currently available.