CVE-2026-0980

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 48% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

February 27, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 2, 2026
Patch available. Sources: redhat.
redhat Patch Available

2429874 – (CVE-2026-0980) CVE-2026-0980 rubyipmi: Red Hat Satellite: Remote Code Execution in rubyipmi via malicious BMC username

https://bugzilla.redhat.com/show_bug.cgi?id=2429874
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-0980
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:5971
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:5970
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:5968

Vendor Advisories for CVE-2026-0980(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrubygem-rubyipmi-0:0.13.0-0.1.el9sat2026-03-26redhat
redhatyggdrasil-worker-forwarder-0:0.0.3-4.el9sat2026-03-26redhat
redhatrubygem-rubyipmi-0:0.13.0-1.el9sat2026-03-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
rubyipmi0.10.0 ... 0.9.3 (19 versions)0.13.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 05:14 UTCEPSS rescore
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-31 16:34 UTCOSV refresh
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:21 UTCEPSS rescore
  18. 2026-08-28 21:40 UTCEPSS rescore
  19. 2026-08-27 14:24 UTCEPSS rescore
  20. 2026-08-25 13:48 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:48 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 45 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 21:08 UTCVendor advisory
  5. 2026-08-14 08:50 UTCEG score recompute
  6. 2026-08-14 08:50 UTCVendor advisory
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 00:48 UTCEG score recompute
  9. 2026-08-13 00:48 UTCVendor advisory
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-11 23:35 UTCEG score recompute
  12. 2026-08-11 23:35 UTCVendor advisory
  13. 2026-08-11 13:42 UTCEPSS rescore
  14. 2026-08-11 06:10 UTCEG score recompute
  15. 2026-08-11 06:10 UTCVendor advisory
  16. 2026-08-10 23:59 UTCEPSS rescore
  17. 2026-08-10 09:05 UTCVendor advisory
  18. 2026-08-09 20:46 UTCEG score recompute
  19. 2026-08-09 20:46 UTCVendor advisory
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 08:28 UTCEG score recompute
  22. 2026-08-09 08:28 UTCVendor advisory
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 08:47 UTCVendor advisory
  25. 2026-08-07 20:29 UTCEG score recompute
  26. 2026-08-07 20:29 UTCVendor advisory
  27. 2026-08-06 13:46 UTCEPSS rescore
  28. 2026-08-06 02:55 UTCEG score recompute
  29. 2026-08-06 02:55 UTCVendor advisory
  30. 2026-08-05 19:17 UTCEPSS rescore
  31. 2026-08-04 15:09 UTCEPSS rescore
  32. 2026-08-04 10:38 UTCEPSS rescore
  33. 2026-08-04 04:54 UTCEG score recompute
  34. 2026-08-04 04:54 UTCVendor advisory
  35. 2026-08-03 10:35 UTCEPSS rescore
  36. 2026-08-02 19:22 UTCEG score recompute▲ 0.50
  37. 2026-08-02 19:22 UTCVendor advisory
  38. 2026-08-02 02:26 UTCEPSS rescore
  39. 2026-08-01 04:15 UTCEPSS rescore
  40. 2026-07-30 16:27 UTCEPSS rescore
  41. 2026-07-30 01:30 UTCEPSS rescore
  42. 2026-07-28 15:36 UTCEPSS rescore
  43. 2026-07-27 14:13 UTCEPSS rescore
  44. 2026-07-27 12:54 UTCEG score recompute
  45. 2026-07-27 12:54 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-0980?
CVE-2026-0980 is a high vulnerability published on February 27, 2026. 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…
When was CVE-2026-0980 disclosed?
CVE-2026-0980 was first published in the National Vulnerability Database on February 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0980 actively exploited?
CVE-2026-0980 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.9% of all scored CVEs.
What is the CVSS score of CVE-2026-0980?
CVE-2026-0980 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-0980?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0980, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0980

Explore →

Is Your Infrastructure Affected by CVE-2026-0980?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs