CVE-2026-18255: Quay: quay: global read-only superuser can view robot account tokens

Published Jul 29, 2026
·
Updated

A flaw was found in Quay. A user configured in GLOBALREADONLYSUPERUSERS is able to view robot account tokens for repositories they are not a member of, allowing an attacker with read-only superuser privileges to impersonate any robot account.

Other sources

Reproduction steps:

1. Configure a user in GLOBALREADONLYSUPERUSERS only. 2. Confirm the same user is not present in SUPERUSERS. 3. Apply config and allow Quay/operator reconciliation. 4. Log in as that user. 5. Navigate to robot account management and token views for a repo they are not a member of. 6. Observe that token visibility is allowed.

Impact: Read-only administrative users can perform actions beyond intended scope. Robot account tokens are persistent by default (they do not expire), and depending on configuration can grant read (pull), write (push), or admin level access to container image repositories.

Red Hat

Affected Software

1 affected component
Quay quay

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Configure GLOBAL_READONLY_SUPER_USERS to include only the specific user(s) that should have read-only superuser privileges. Do not include additional users.

    Quay GLOBAL_READONLY_SUPER_USERS = Remove any unintended users; configure only the required user(s)
  2. Configuration

    Confirm that the user configured in GLOBAL_READONLY_SUPER_USERS is not also present in SUPER_USERS.

    Quay SUPER_USERS = Ensure the same user is not present
  3. Compensating control

    Apply configuration changes and allow Quay/operator reconciliation so the corrected GLOBAL_READONLY_SUPER_USERS/SUPER_USERS settings take effect.

Event History

Jul 29, 2026
Data Sourced
via Red Hat·03:52 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·04:34 PM
Data Sourced
via MITRE·04:34 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-18255?

CVE-2026-18255 has a high severity rating of 7.2.

2

How can I fix CVE-2026-18255?

To mitigate CVE-2026-18255, ensure that sensitive user roles are not configured in GLOBAL_READONLY_SUPER_USERS.

3

What are the implications of CVE-2026-18255?

CVE-2026-18255 allows a user with read-only superuser privileges to access robot account tokens for repositories they do not belong to, leading to potential impersonation.

4

What software is affected by CVE-2026-18255?

CVE-2026-18255 affects Quay, specifically the Quay software used for container image storage.

5

When was CVE-2026-18255 published?

CVE-2026-18255 was published on July 29, 2026.

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