Red Hat Quay 3 auth bypass in robot account password handling
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Summary
Red Hat Quay 3 accepts restricted, short-lived registry tokens as robot account passwords. A remote attacker who already holds such a token and can log in can use it to authenticate as the robot account, gain broader permissions, and keep generating new tokens even after the robot account's password is reset.
Written by a model
Original 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.
Who should check
Teams running Red Hat Quay deployments that issue robot account tokens, such as CI pipelines that push and pull images.
“In Red Hat Quay deployments, an exposed bearer token”
What to do
Check whether your setup matches what the bug needs.
Attacker already holds a valid, scoped registry token minted for a robot account. Deployment is a Red Hat Quay deployment.Workaround: The checked facts give no workaround. Resetting the robot account's password alone is not enough, because the facts say the attacker can keep minting fresh tokens afterward.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134651 (Quay: quay: registry jwt accepted as robot password enables privilege elevation), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134651 (entry last updated 2026-11-22):
Affected:
- Red Hat Red Hat Quay 3: version range not reported
- Red Hat Red Hat Quay 3: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Attacker already holds a valid, scoped registry token minted for a robot account. (source: https://access.redhat.com/security/cve/cve-2026-134651)
- Deployment is a Red Hat Quay deployment. (source: https://access.redhat.com/security/cve/cve-2026-134651)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134651 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134651 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2580912
- https://access.redhat.com/security/cve/CVE-2026-134651
- https://access.redhat.com/security/cve/cve-2026-134651
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134651
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134651"}.Affected versions
- quay/quay-rhel8Version range not reported
- quay/quay-rhel9Version range not reported
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity6.8/10CVSS 6.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 37 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134651 |
| Record | NVD · CVE-2026-134651 |
| Write-ups 1Establishes: Technical detail and context. | |
| Report | bugzilla.redhat.com · show_bug.cgi?id=2580912 |
| Other links 1 | |
| Link | access.redhat.com · security/cve/CVE-2026-134651 |
Questions about CVE-2026-134651
Is CVE-2026-134651 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A registry JWT, the bearer token minted for a robot account, is accepted as that robot account's password. An authenticated attacker who already holds such a scoped token can log in as the robot account and gain broader permissions, and can keep minting fresh tokens even after the robot account's password is reset.
Source: access.redhat.com
Am I affected, and how do I check?
The checked facts list Red Hat Quay 3 but give no version range. The issue needs a valid, scoped registry token minted for a robot account, so check your Quay version and whether robot account tokens are in use.
Source: access.redhat.com
How do I fix CVE-2026-134651?
The checked facts name no fixed version and no patch identifiers, so consult Red Hat's advisory for the fix before deciding on an upgrade.
Source: access.redhat.com
What if there's no patch?
The checked facts give no workaround. Resetting the robot account's password alone is not enough, because the facts say the attacker can keep minting fresh tokens afterward.
Source: access.redhat.com
Related
- CVE-2026-110697Quay: quay: sql like wildcard injection in robot listing leaks cross-tenant robot tokens
- CVE-2026-123710Quay: red hat quay: unauthenticated registry signing-key takeover via service key rotation
- CVE-2026-85469Quay-builder-qemu: quay-builder-qemu: release workflow uses third-party action pinned to mutable @master with registry credentials in scope
- CVE-2026-74243Quay: unauthenticated secscan notification endpoint in quay when psk is unset
- CVE-2026-85471Quay: quay: webhook notification ssrf -- hostname-string blocklist trivially bypassable
- CVE-2026-109194Quay: build trigger uuid idor in quay api
No corrections so far. Something wrong on this page? Report an error.