Skip to main content
CVE-2026-134651VulnerabilityPublished

Quay. This vulnerability · CWE-303

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134651· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium.

Data as of 22 Nov 2026, 07:26 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, no mitigation or patch meeting Red Hat's criteria for ease of use, applicability, and stability is available. Users should protect scoped registry tokens from exposure, such as avoiding leakage in continuous integration logs. Monitor Red Hat advisories for future fixes or mitigations. Customers with Red Hat Technical Account Managers can consult them for tailored guidance.

Description

A vulnerability in Red Hat Quay allows an authenticated attacker with a restricted, short-lived JSON Web Token (JWT) scoped for a robot account to escalate privileges. The flaw arises because Quay improperly accepts scoped registry bearer tokens as valid robot account passwords, enabling direct authentication as the robot account and broader permissions. This unauthorized access persists even after the robot account's password is reset, allowing the attacker to generate fresh tokens. Exploitation requires possession of a valid scoped registry token, such as one leaked through CI logs. The vulnerability does not grant permissions beyond those already authorized for the robot account.

References

Community reviews

Loading reviews…