CVE-2026-107444 in Hardened Images
Summary
by MITRE • 10/08/2026
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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 10/08/2026
The vulnerability identified within Katello represents a critical failure in access control logic, specifically concerning how organizational scoping is enforced for Docker meta-tag repositories. In multi-tenant environments where data isolation between organizations is paramount, this flaw allows an authenticated user to bypass intended security boundaries. The core technical issue lies in the API endpoint responsible for listing repositories associated with a specific Docker tag. Instead of validating that the requested resource belongs to the same organization as the requesting user or restricting access based on the user's organizational context, the system relies solely on the provided tag identifier. This design oversight means that if an attacker can discover or guess valid tag identifiers from other organizations, they can directly query the API without triggering any authorization checks related to organizational ownership.
From a technical perspective, this is a classic example of insecure direct object references combined with broken access control. The application fails to perform proper vertical and horizontal privilege escalation prevention mechanisms when handling requests for Docker metadata. While the user may have legitimate permissions to view products within their own assigned organization, the API endpoint does not cross-reference these credentials against the organizational attributes of the target repository or tag. Consequently, the system treats all valid tag identifiers as accessible regardless of who owns them, provided the requester is authenticated and has at least minimal product viewing rights elsewhere in the system. This lack of context-aware validation creates a direct path for information disclosure across isolated tenant boundaries.
The operational impact of this vulnerability is significant for organizations relying on Katello for container image management and distribution. An attacker with low-level access can enumerate repository configurations, including names, descriptions, and potentially other metadata associated with Docker tags from competing or unrelated internal departments. This unauthorized disclosure compromises the confidentiality of sensitive infrastructure details. Knowledge of specific repository structures can aid in further reconnaissance efforts, allowing an adversary to map out the organization's container ecosystem more effectively than intended. In severe cases where additional vulnerabilities exist within those repositories themselves, this information could facilitate targeted attacks against downstream systems that consume these images.
This flaw aligns with CWE-284, which describes Improper Access Control, and specifically relates to CWE-639, Authorization Bypass Through User-Controlled Key. The attack vector is consistent with MITRE ATT&CK technique T1078, Valid Accounts, as it requires authentication but exploits the lack of proper authorization checks for specific resources. It also touches upon T1528, Steal Application Access Token, if the metadata reveals tokens or keys embedded in repository configurations, though primarily it serves as a reconnaissance tool under T1592, Gather Victim Host Information. The severity is heightened by the fact that Docker tags are often central to deployment pipelines, making their exposure particularly risky for supply chain security.
Mitigation strategies must focus on enforcing strict organizational scoping at the API level. Developers should modify the repository listing logic to ensure that every request includes a validation step confirming that the target resource belongs to an organization associated with the authenticated user's session or assigned roles. Implementing role-based access control checks that explicitly verify ownership before returning data is essential. Additionally, applying principle of least privilege ensures that users only have visibility into resources they are explicitly permitted to see. Regular security audits and penetration testing focused on cross-tenant isolation can help identify similar flaws in other API endpoints within the Katello ecosystem.