Skip to content
Fencer Vulns
medium 4.5

CVE-2026-8058 json

This Power System update is being released to address a sensitive information disclosure

published 2026-07-28 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-49885

cvss
4.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

IBM OPENBMC FW1110.00 through FW1110.20, and FW1060.00 through FW1060.71 allows a user to supply a password with a resource dump request stores that password into the BMC audit log where an admin user can see it.

Patch / fix

  • ibm power_system_s1122_(9824-22a)_firmware fw1110.30
  • ibm power_system_s1124_(9824-42a)_firmware fw1110.30
  • ibm power_system_s1122s_(9824-22b)_firmware fw1110.30
  • ibm power_system_s1114_(9824-41b)_firmware fw1110.30
  • ibm power_system_l1122_(9856-22h)_firmware fw1110.30
  • ibm power_system_l1124_(9856-42h)_firmware fw1110.30
  • ibm power_system_e1150_(9043-mru)_firmware fw1110.30
  • ibm power_system_s1022_(9105-22a)_firmware fw1060.72
  • ibm power_system_s1024_(9105-42a)_firmware fw1060.72
  • ibm power_system_s1022s_(9105-22b)_firmware fw1060.72
  • ibm power_system_s1014_(9105-41b)_firmware fw1060.72
  • ibm power_system_l1022_(9786-22h)_firmware fw1060.72
  • ibm power_system_l1024_(9786-42h)_firmware fw1060.72
  • ibm power_system_e1050_(9043-mrx)_firmware fw1060.72
  • ibm power_system_s1012_(9028-21b)_firmware fw1060.72

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected products

  • IBM OPENBMC

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.