Quick answers
- Is CVE-2026-79654 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-79654 being exploited in the wild.
- How severe is CVE-2026-79654?
- Medium severity, with a CVSS score of 4.3, published 26 August 2026.
- Which products and versions are affected?
- Red Hat Katello <UNKNOWN>.
- Is there a fix for CVE-2026-79654?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-79654 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-79654?
- Check whether you run Red Hat Katello at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass (CWE-639) in Katello's Content View History API endpoint. An authenticated user with view_content_views permission in one organization can access the lifecycle history of Content Views belonging to another organization by providing the Content View's identifier. The API fails to properly enforce authorization checks on the specified Content View resource. No user interaction is required; the attack is network-accessible and requires only a valid authenticated session with minimal privileges. The exposure is limited to unauthorized disclosure of Content View metadata (publication events, promotion events, usernames, timestamps) and does not grant access to repository contents, credentials, or modification capabilities.
Affected products
- Red Hat Katello <UNKNOWN>
Timeline
- 2026-08-26: disclosed
- other: GitHub PR 11847 and Bugzilla 2523348 reference fixes