CVE-2026-79654: Ketello: katello content view history api cross-organization authorization bypass
A flaw was found in Katello where the Content View History API does not properly enforce authorization when accessing a Content View specified by the user. An authenticated user with permission to view Content Views in one organization may be able to access the lifecycle history of a Content View belonging to another organization by supplying its identifier to the affected API endpoint. This can result in unauthorized disclosure of Content View lifecycle information, including publication and promotion events, associated users, and timestamps.
Other sources
An authorization bypass in Katello's Content View History API. The ContentViewHistoriesController resolves the requested Content View using an unrestricted ContentView.find(params[:contentviewid]) lookup instead of the authorization-aware ContentView.readable scope. As a result, an authenticated user with viewcontentviews permission for one organization may be able to supply the ID of a Content View belonging to another organization and retrieve its lifecycle history. The reported impact is limited to unauthorized disclosure of Content View lifecycle metadata, including publication and promotion events, associated users, and timestamps.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user who has permission to view Content Views in at least one organization can potentially exploit it. The user does not need permissions for the organization that owns the targeted Content View.
What information could be exposed?
The affected API may disclose lifecycle history for a Content View in another organization. Exposed information can include publication and promotion events, associated users, and timestamps.
What does an attacker need to target another organization's Content View?
The attacker needs the identifier of the Content View belonging to the other organization and must supply it to the affected API endpoint. No user interaction is required.