CVE-2026-134651: Quay: quay: registry jwt accepted as robot password enables privilege elevation

Published Nov 21, 2026
·
Updated

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.

Other sources

A flaw was found in Quay's robot credential verification path. In data/model/user.py, verifyrobot() treats a JWT-shaped password as a robot credential and calls verifyrobotjwttoken(), which checks mainly signature, sub, and aud. Registry bearer tokens minted by /v2/auth for a robot do not carry apiscopes; auth/credentials.py therefore does not take the robot API JWT path and falls through to verifyrobot(). As a result, a Quay-signed registry JWT whose sub is the robot is accepted as that robot's password. An attacker who obtains a scoped, short-lived registry JWT (for example pull-only on one repository, via CI log or config.json exposure) can authenticate as the full robot, request broader registry scopes the robot is already entitled to, and continue minting fresh tokens via /v2/auth. Regenerating the robot's stored password does not revoke this path; access ends when the robot is deleted, the owner is disabled, or the robot's repository permissions are removed. This was reproduced locally: a pull-only registry JWT used as basic-auth password successfully reminted a push+pull token, and the same JWT continued to work after robot password regeneration while the old password returned 401.

— Red Hat

Affected Software

1 affected component
Red Hat Quay

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    To end access through this path, delete the affected robot, disable its owner, or remove the robot's repository permissions.

Event History

Nov 21, 2026
Data Sourced
via Red Hat·10:45 PM
DescriptionSeverityAffected Software
Nov 22, 2026
CVE Published
via MITRE·05:05 AM
Data Sourced
via MITRE·05:05 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:18 AM
DescriptionSeverityWeakness

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203