Skip to main content
VulnerabilityPublished

CVE-2026-134651: Red Hat Quay 3 · Incorrect Implementation of Authentication Algorithm

Affects Red Hat Quay 3Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium.

Data as of 22 Nov 2026, 05:24 UTC

CVSS 3.1 base score
6.8Medium
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.16.8
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Quay 3quay/quay-rhel8Affected–Fixed in–
Red Hat Quay 3quay/quay-rhel9Affected–Fixed in–

AI-suggested

Currently, there is no available fix or mitigation that meets Red Hat's criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat's advisory for updates. Since exploitation requires possession of a valid scoped registry token, protecting such tokens from leakage (e.g., in CI logs) is critical. Red Hat Product Security recommends upgrading to a supported version with a fix once available.

Description

CVE-2026-134651 is a vulnerability in Red Hat Quay 3 where the software incorrectly accepts scoped registry bearer tokens as valid robot account passwords. This flaw allows an authenticated attacker with a restricted, short-lived JSON Web Token (JWT) to escalate privileges by authenticating directly as the robot account and gaining broader permissions. The unauthorized access persists even after the robot account's password is reset, enabling the attacker to generate fresh tokens. Exploitation requires possession of a valid scoped registry token for a robot account, limiting the scope of compromise to the permissions already granted to that account.

References

Community reviews

Loading reviews…