VulnerabilityPublished 13 Nov 2026

CVE-2026-128824: mirror registry for Red Hat OpenShift 2 · Cross-site Scripting

Affects mirror registry for Red Hat OpenShift 2Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 13 Nov 2026, 09:29 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	5.4

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 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 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
mirror registry for Red Hat OpenShift 2openshift/mirror-registry-rhel8	Affected–	Fixed in–
Red Hat Quay 3quay/quay-rhel9	Affected–	Fixed in–

AI-suggested

Red Hat currently does not provide an official fix or mitigation that meets their product security criteria for this vulnerability. Users should be aware that anonymous access to public repositories is enabled by default, which facilitates exploitation. Until a fix is released, mitigation options are limited. Monitoring Red Hat's advisory page for updates and avoiding clicking on untrusted URLs related to the Quay registry is recommended.

Description

A reflected cross-site scripting (XSS) vulnerability exists in Red Hat Quay's v1 registry API error handler. The flaw allows attacker-supplied input in the image_id path segment to be reflected in an HTML response, enabling execution of arbitrary JavaScript in the victim's browser when visiting a crafted URL. Exploitation requires user interaction and anonymous access to a public repository, which is enabled by default. No official fix or mitigation meeting Red Hat's criteria is currently available.

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the victim's browser within the Quay origin, potentially compromising user sessions and confidentiality. The vulnerability has a CVSS v3.1 score of 5.4 (medium severity) with low complexity and no privileges required, but user interaction is necessary. The impact includes disclosure of private information such as session cookies and possible unauthorized actions performed on behalf of the victim.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 09:29 UTC

Technical details

References

Community reviews

Related threats