CVE-2026-0980: Rubyipmi: red hat satellite: remote code execution in rubyipmi via malicious bmc username

Published Jan 15, 2026
·
Updated

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.

Other sources

Summary: Authorized RCE in Red Hat Satellite via rubyipmi gem used in the BMC component

Requirements to exploit: Satellite with the BMC component enabled, using ipmitool as the IPMI implementation. The attacker needs permissions to create (or update) existing hosts in Satellite, but not to manage Satellite.

Component affected: https://github.com/logicminds/rubyipmi

Version affected: <= 0.12.1

Patch available: yes

Version fixed (if any already): none yet

CVSS (optional): I don't believe in CVSS

Impact (optional): moderate

Embargo: no

Reason: one needs a specific setup and privileges in it to be able to exploit Suggested public date: dd-MMM-yyyy (It is important to note that an embargo may be lifted before there is a fix if necessary)

Acknowledgement: <Name> <Company> of the reporter and if they want to be acknowledged

Steps to reproduce if available:

deploy Foreman/Satellite with --foreman-proxy-bmc true create a host with a BMC interface and use "admin; touch /var/log/foreman-proxy/hacked" as the username for the BMC (requires host create/edit permissions, but not admin) refresh the host in the UI for Foreman to fetch the BMC status see /var/log/foreman-proxy/hacked was created Mitigation if available: use freeipmi or apply patch

Red Hat

Affected Software

4 affected componentsFixes available
redhat/rubyipmi<=0.12.1
rubygems/rubyipmi<0.13.0
0.13.0
redhat Satellite=6.0
logicminds rubyipmi<=0.12.1

Event History

Jan 15, 2026
Data Sourced
via Red Hat·08:51 AM
DescriptionSeverityAffected Software
Feb 27, 2026
CVE Published
via MITRE·07:30 AM
Data Sourced
via MITRE·07:30 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 AM
Affected Software
Advisory Published
via GitHub·09:30 AM
Data Sourced
via GitHub·09:30 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-0980?

CVE-2026-0980 is classified as a high-severity vulnerability due to its potential to allow remote code execution.

2

How do I fix CVE-2026-0980?

To fix CVE-2026-0980, update rubyipmi to version 0.13.0 or later.

3

What systems are affected by CVE-2026-0980?

CVE-2026-0980 affects rubyipmi versions up to 0.12.1 and Red Hat Satellite version 6.0.

4

What types of attacks can exploit CVE-2026-0980?

CVE-2026-0980 can be exploited by authenticated attackers with host creation or update permissions to execute malicious code.

5

Is there a way to mitigate CVE-2026-0980 without updating?

There are no known mitigations for CVE-2026-0980 aside from updating to a patched version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203