Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 22 Nov 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Red Hat
Red Hat red Hat Quay 3 Redhat quay 3 Redhat red Hat Quay 3 |
|
| Vendors & Products |
Red Hat
Red Hat red Hat Quay 3 Redhat quay 3 Redhat red Hat Quay 3 |
Sun, 22 Nov 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Sun, 22 Nov 2026 05:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Quay. This vulnerability allows an authenticated remote attacker holding a restricted, short-lived JSON Web Token (JWT) to achieve privilege escalation. Because Quay improperly accepts scoped registry bearer tokens as valid robot account passwords, an attacker can authenticate directly as the robot account and obtain broader permissions. Consequently, unauthorized access persists and enables the attacker to generate fresh tokens even after the robot account's password has been reset. | |
| Title | Quay: quay: registry jwt accepted as robot password enables privilege elevation | |
| First Time appeared |
Redhat
Redhat quay |
|
| Weaknesses | CWE-303 | |
| CPEs | cpe:/a:redhat:quay:3 | |
| Vendors & Products |
Redhat
Redhat quay |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-11-22T05:05:52.562Z
Reserved: 2026-11-21T22:39:37.197Z
Link: CVE-2026-134651
No data.
Status : Awaiting Analysis
Published: 2026-11-22T05:18:43.660
Modified: 2026-11-22T05:18:43.820
Link: CVE-2026-134651
OpenCVE Enrichment
Updated: 2026-11-22T14:45:12Z