ibm power system s1022s (9105-22b) firmware
productUScpe:2.3:o:ibm:power_system_s1022s_\(9105-22b\)_firmware:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
0critical3high8medium2low
updated 2026-10-27
| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2026-7868US | high8.8OT elevated | 0.37% (30th) | — | ✓fw1060.72 | 2026-07-28 | fw1060.00 → fw1060.72 |
| CVE-2026-18849US | — | 0.37% (30th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-8058US | medium4.9 | 0.36% (29th) | — | ✓fw1060.72 | 2026-07-28 | fw1060.00 → fw1060.72 |
| CVE-2026-17414US | high8.8 | 0.30% (22nd) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-18821US | high8.8 | 0.29% (21st) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-17028US | — | 0.28% (20th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-16724US | — | 0.26% (17th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-18870US | medium4.3 | 0.18% (8th) | — | ✓fw1060.82 | 2026-09-24 | fw1060.00 → fw1060.82 |
| CVE-2026-16930US | —OT elevated | 0.17% (7th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-16933US | — | 0.17% (6th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-16707US | — | 0.17% (6th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-16661US | — | 0.17% (6th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-17100US | — | 0.17% (6th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-17093US | — | 0.17% (6th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-19234US | — | 0.17% (6th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-17063US | —OT elevated | 0.16% (5th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-19321US | — | 0.16% (5th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-17429US | —OT elevated | 0.15% (4th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-17091US | — | 0.15% (4th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-11885US | — | 0.15% (4th) | — | ✓fw1060.72 | 2026-07-30 | fw1060.00 → fw1060.72 |
| CVE-2026-17097US | medium6.7 | 0.14% (4th) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-18871US | — | 0.14% (3rd) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-17511US | low3.4 | 0.13% (3rd) | — | ✓fw1060.82 | 2026-09-24 | fw1060.00 → fw1060.82 |
| CVE-2026-4937US | medium6.0 | 0.13% (3rd) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-15961US | medium6.0 | 0.13% (3rd) | — | ✓fw1060.81 | 2026-08-19 | fw1060.00 → fw1060.81 |
| CVE-2026-19492US | low3.2 | 0.11% (2nd) | — | ✓fw1060.82 | 2026-09-24 | fw1060.00 → fw1060.82 |
| CVE-2026-4932US | medium4.6 | 0.11% (1st) | — | ✓fw1060.72 | 2026-07-28 | fw1060.00 → fw1060.72 |
| CVE-2026-18857US | — | 0.11% (1st) | — | ✓fw1060.82 | 2026-09-24 | fw1060.00 → fw1060.82 |
| CVE-2026-4936US | medium6.2 | 0.10% (1st) | — | ✓fw1060.72 | 2026-08-19 | fw1060.00 → fw1060.72 |
| CVE-2026-17504US | medium4.4 | 0.10% (1st) | — | ✓fw1060.81 | 2026-09-24 | fw1060.00 → fw1060.81 |
| CVE-2026-17503US | — | 0.10% (1st) | — | ✓fw1060.82 | 2026-09-24 | fw1060.00 → fw1060.82 |
| CVE-2026-17413US | — | 0.10% (1st) | — | ✓fw1060.82 | 2026-09-24 | fw1060.00 → fw1060.82 |