VulnerabilityPublished 27 Feb 2026Updated 26 Mar 2026

CVE-2026-0980: Red Hat Satellite 6.16 for RHEL 8 · OS Command Injection

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

Compare

Not known to be exploited · CVSS 8.3 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

8.3High

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

EPSS: 0.8% chance of exploitation in 30 days – higher than 58% 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:H/I:H/A:L

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

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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Feb 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 30 Oct 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.17 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Satellite 6.17 for RHEL 9	Affected–	Fixed in–
Red HatRed Hat Satellite 6.17 for RHEL 9	Affected–	Fixed in–

AI-suggested

Organizations should immediately review and restrict host creation and update permissions within Red Hat Satellite to trusted administrators only, minimizing the number of users who can exploit this vulnerability. Applying the official security patch from Red Hat as soon as it becomes available is the most effective mitigation. Until patches are applied, consider implementing network segmentation and firewall rules to limit access to the Red Hat Satellite management interfaces, especially the BMC components. Audit and monitor logs for unusual activity related to host creation or updates, and deploy intrusion detection systems tuned to detect command injection patterns. Employ strict input validation and sanitization on any custom scripts or automation interacting with the BMC interface. Additionally, conduct a thorough review of user accounts with elevated permissions and enforce multi-factor authentication to reduce the risk of credential compromise. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.

Description

A flaw was found in rubyipmi, a gem used in the Baseboard Management Controller (BMC) component of Red Hat Satellite. An authenticated attacker with host creation or update permissions could exploit this vulnerability by crafting a malicious username for the BMC interface. This could lead to remote code execution (RCE) on the system.

Impact

The exploitation of CVE-2026-0980 can lead to remote code execution on systems running Red Hat Satellite 6.16 for RHEL 8, resulting in full compromise of system confidentiality and integrity, and partial impact on availability. Attackers gaining RCE can manipulate or exfiltrate sensitive configuration data, deploy malware, disrupt infrastructure management, or pivot to other internal systems. Since Red Hat Satellite is used for provisioning and managing large numbers of servers, a successful attack could cascade, affecting multiple systems and services within an organization. The requirement for authenticated access with host creation or update permissions limits the attack surface but does not eliminate risk, especially in environments with many administrators or automated processes. The impact is particularly severe for organizations relying on Red Hat Satellite for critical infrastructure management, including cloud providers, financial institutions, government agencies, and large enterprises. The absence of known exploits in the wild provides a window for remediation, but the high severity score demands urgent attention.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 18:28 UTC

Technical details

References

Community reviews

Related threats