Ketello: katello content view history api cross-organization authorization bypass
Red Hat · Red Hat Satellite 6.16 for RHEL 8
Official source article: Red Hat RHSA-2026:74503 ↗. Check the applicable product and release in the original source.
4.3MediumCVSS 3.1
Recommended action
Scheduled
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Evidence used
No CISA KEV confirmation is currently recorded.
EPSS is 0.37% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Monitor vendor guidance and exploitation sources for a material change.
Verification
Confirm that the asset runs Red Hat Red Hat Satellite 6.16 for RHEL 8 and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Direct vendor intelligence
Authoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
1 current
CVE-2026-79654 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityketello: Katello Content View History API Cross-Organization Authorization Bypass
1 known affected
The vendor explicitly identifies these products as affected by this CVE.
satellite:el8/rubygem-katello.src as a component of Red Hat Satellite 6
Summary
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.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with Redhat family set. Attempts to download a unattended template without valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data.
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-66252
No EUVD known-exploited evidence
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.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
4.3 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available
01
What, why and how
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.
What
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.
Why
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.None recorded
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
Likely attack path
a network path → Authorization Bypass Through User-Controlled Key → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-639: Authorization Bypass Through User-Controlled Key. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-639
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2026-66252Official EUVD mapping
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.
Official EUVD record ↗Cyber Security Agency of Singapore · English · CSA-SB-20260902Security Bulletin 2 Sept 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 2 Sept 2026, published on 2 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.16/html/updating_red_hat_satellite/index Release Notes: Provisioning tokens are now required for all Operating System entries with Redhat family set. Attempts to download a unattended template without valid token will lead to “a provisioning token is required but a valid one was not provided” error. This changed behavior will lead to inability to use Generic or Subnet Bootdisks, systems using this bootdiks will be not matched with the host entry and not boot. To use Bootdisk after applying the errata, either use Full Host Bootdisk which uses tokens, or set Administer - Settings - Provisioning - Installation token lifetime to zero. This turns off the token enforcement and allows unauthenticated parties to use arbitrary MAC addresses in unattended requests to fetch provisioning kickstart with possibly sensitive data.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 26 Aug 2026 · Last source change 2 Oct 2026, 17:36 UTC · CWE-639 · Authorization Bypass Through User-Controlled Key
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-08-26
European sourceENISA EUVD · EUVD-2026-66252
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
See the vendor and CVE records for the affected range. · Fixed: Red Hat Satellite 6.16 for RHEL 8: 0:4.14.0.23-1.el8sat < *; Red Hat Satellite 6.16 for RHEL 9: 0:4.14.0.23-1.el9sat < *; Red Hat Satellite 6.18 for RHEL 9: 0:4.18.0.24-1.el9sat < *; Red Hat Satellite 6.19 for RHEL 9: 0:4.20.0.11-1.el9sat < *
After
See the vendor and CVE records for the affected range. · Fixed: Red Hat Satellite 6.16 for RHEL 8: 0:4.14.0.23-1.el8sat < *; Red Hat Satellite 6.16 for RHEL 9: 0:4.14.0.23-1.el9sat < *; Red Hat Satellite 6.17 for RHEL 9: 0:4.16.0.20-1.el9sat < *; Red Hat Satellite 6.18 for RHEL 9: 0:4.18.0.24-1.el9sat < *; Red Hat Satellite 6.19 for RHEL 9: 0:4.20.0.11-1.el9sat < *
Affected versionsThe structured affected or fixed version information changed.
Before
satellite:el8/rubygem-katello.src as a component of Red Hat Satellite 6 · Fixed: rubygem-katello-0:4.20.0.11-1.el9sat.noarch as a component of Red Hat Satellite 6.19 for RHEL 9; rubygem-katello-0:4.20.0.11-1.el9sat.src as a component of Red Hat Satellite 6.19 for RHEL 9
After
satellite:el8/rubygem-katello.src as a component of Red Hat Satellite 6 · Fixed: rubygem-katello-0:4.14.0.23-1.el8sat.noarch as a component of Red Hat Satellite 6.16 for RHEL 8; rubygem-katello-0:4.14.0.23-1.el8sat.src as a component of Red Hat Satellite 6.16 for RHEL 8; rubygem-katello-0:4.14.0.23-1.el9sat.noarch as a component of Red Hat Satellite 6.16 for RHEL 9; rubygem-katello-0:4.14.0.23-1.el9sat.src as a component of Red Hat Satellite 6.16 for RHEL 9; rubygem-katello-0:4.16.0.20-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9; rubygem-katello-0:4.16.0.20-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9; rubygem-katello-0:4.18.0.24-1.el9sat.noarch as a component of Red Hat Satellite 6.18 for RHEL 9; rubygem-katello-0:4.18.0.24-1.el9sat.src as a component of Red Hat Satellite 6.18 for RHEL 9; rubygem-katello-0:4.20.0.11-1.el9sat.noarch as a component of Red Hat Satellite 6.19 for RHEL 9; rubygem-katello-0:4.20.0.11-1.el9sat.src as a component of Red Hat Satellite 6.19 for RHEL 9
Affected versionsThe structured affected or fixed version information changed.
Before
See the vendor and CVE records for the affected range. · Fixed: Red Hat Satellite 6.19 for RHEL 9: 0:4.20.0.11-1.el9sat < *
After
See the vendor and CVE records for the affected range. · Fixed: Red Hat Satellite 6.16 for RHEL 8: 0:4.14.0.23-1.el8sat < *; Red Hat Satellite 6.16 for RHEL 9: 0:4.14.0.23-1.el9sat < *; Red Hat Satellite 6.18 for RHEL 9: 0:4.18.0.24-1.el9sat < *; Red Hat Satellite 6.19 for RHEL 9: 0:4.20.0.11-1.el9sat < *
Affected versionsThe structured affected or fixed version information changed.
Before
rubygem-katello.src as a component of Red Hat Satellite 6; satellite:el8/rubygem-katello.src as a component of Red Hat Satellite 6
After
satellite:el8/rubygem-katello.src as a component of Red Hat Satellite 6 · Fixed: rubygem-katello-0:4.20.0.11-1.el9sat.noarch as a component of Red Hat Satellite 6.19 for RHEL 9; rubygem-katello-0:4.20.0.11-1.el9sat.src as a component of Red Hat Satellite 6.19 for RHEL 9
Affected versionsThe structured affected or fixed version information changed.
Before
rubygem-katello.src as a component of Red Hat Satellite 6; tfm-rubygem-katello as a component of Red Hat Satellite 6; tfm-rubygem-katello.src as a component of Red Hat Satellite 6; tfm-rubygem-katello_ostree as a component of Red Hat Satellite 6
After
rubygem-katello.src as a component of Red Hat Satellite 6
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.