CVE-2026-107444: Rubygem-katello: katello docker tags repositories api cross-organization authorization bypass

Published Oct 8, 2026
·
Updated

A flaw was found in Katello where the Docker Tags repositories API does not properly enforce organization scoping when listing repositories for a Docker meta tag. An authenticated user with permission to view products in one organization may be able to retrieve repository metadata associated with Docker tags belonging to another organization by supplying the tag identifier. This can result in unauthorized disclosure of repository configuration information across organization boundaries.

Other sources

A flaw was found in Katello. The Docker Tags repositories API endpoint resolves a DockerMetaTag with an unscoped find and returns associated repositories without intersecting Repository.readable. An authenticated user with viewproducts permission in one organization can enumerate repository metadata (names, product associations, content types, upstream URLs) for Docker tags belonging to other organizations by supplying the tag identifier and omitting the optional organization filter. Reported via PSIRTSUPT-25120.

— Red Hat

Affected Software

1 affected component
rubygem/katello

Event History

Oct 8, 2026
Data Sourced
via Red Hat·03:31 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·03:41 AM
Data Sourced
via MITRE·03:41 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated user who has permission to view products in one organization can exploit it. The user does not need access to the organization whose Docker tag repository metadata is disclosed.

2

What information could be exposed?

The issue can disclose repository metadata associated with Docker tags in other organizations, including repository names, product associations, content types, and upstream URLs. The provided information does not indicate that repository contents or write access are exposed.

3

What request condition triggers the authorization bypass?

The user supplies the identifier of a Docker meta tag belonging to another organization and omits the optional organization filter. The affected API resolves the tag without organization scoping and does not limit returned repositories to those the requester can read.

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