CVE-2026-107444
Description
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.
Statement
A MODERATE severity information disclosure flaw was found in Katello, as shipped in Red Hat Satellite 6. The Docker Tags repositories API endpoint resolves a Docker meta tag with an unscoped lookup and returns its associated repositories without restricting the results to repositories readable by the requesting user. Consequently, an authenticated user who has permission to view products in one organization can supply the identifier of a Docker tag belonging to another organization and, by omitting the optional organization filter, retrieve repository metadata from that other organization, including repository names, product associations, content types, and upstream URLs. The flaw affects the confidentiality of repository configuration information only; there is no impact on integrity or availability. Both Red Hat and the upstream CVE assessment rate this flaw MODERATE with a CVSS 3.1 score of 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). Red Hat Satellite 6.16, 6.17, 6.18, and 6.19 are affected, and the fix is currently deferred because the impact is MODERATE with a CVSS score below 7.0; the residual risk is that an authenticated user with view_products permission may enumerate repository metadata across organization boundaries. The Red Hat Hardened Images (Hummingbird) product is not affected because the vulnerable Katello component is not present in it.
Mitigation
Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when/if they become available.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.3 | N/A | 4.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Access control checks for specific user data or functionality can be bypassed.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Horizontal escalation of privilege is possible (one user can view/modify information of another user).
Access Control
Technical Impact: Gain Privileges or Assume Identity
Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.
Acknowledgements
Red Hat would like to thank Aditya Dixit (Credshields) for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
