VulnerabilityPublished 1 Jul 2026

CVE-2026-5135: Red Hat Satellite 6.16 for RHEL 8 · Insecure Direct Object Reference

Affects Red Hat Satellite 6.16 for RHEL 8Source CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red HatRed Hat Satellite 6.16 for RHEL 8	Affected–	Fixed in–
Red HatRed Hat Satellite 6.16 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Satellite 6.17 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Satellite 6.18 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Satellite 6.19 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Satellite 6	Affected–	Fixed in–

AI-suggested

Until a fix is available, restrict host-edit permissions to trusted users only and monitor for unusual configuration changes. Follow vendor updates closely for any official fixes or workarounds.

Description

A flaw was found in Foreman. This broken access control vulnerability allows an authenticated user with host-edit permissions to retarget an existing lookup value override to a different host. This is achieved by modifying the match field through nested host attributes, effectively bypassing authorisation checks. The consequence is the potential for unauthorised modification of managed host configurations across different organisational and location boundaries.

Impact

An attacker with legitimate host-edit permissions can modify configuration overrides on hosts outside their authorized scope, potentially affecting hosts across different organizational units or locations. This unauthorized modification can lead to integrity issues in managed host configurations, possibly disrupting management policies or causing misconfigurations.

Summary

This vulnerability in Red Hat Satellite 6 arises from improper authorization checks in the Foreman component. An authenticated user who has host-edit permissions can manipulate the match field through nested host attributes to retarget lookup value overrides to hosts they should not control. This effectively bypasses access controls and allows unauthorized changes to managed host configurations. No official remediation or patch is currently confirmed in the vendor advisory. The CVSS 3.1 vector indicates network attack vector, low attack complexity, requires privileges, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Jul 2026, 14:54 UTC

Technical details

References

Community reviews

Related threats