← Search results
CVE-LINKED INVENTORY37 SECURITY RECORDS
IBM
PowerVM Hypervisor
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-19492 | 24 Sep 2026 | PowerVM Hypervisor: FW1120.00 ≤ FW1120.01, FW1110.00 ≤ FW1110.31, FW1060.00 ≤ FW1060.81 | Customers with the products below should install FW1110.32(1110_138), FW1120.02(1120_171), or newer to remediate this vulnerability.; Power 11; * IBM Power System E1180 (9080-HEU); Customers with the products below should install FW1110.32(1110_160), FW1120.02(1120_195), or newer to remediate this vulnerability.; * IBM Power System S1122 (9824-22A); * IBM Power System S1124 (9824-42A); * IBM Power System S1122s (9824-22B); * IBM Power System S1114 (9824-41B); * IBM Power System L1122 (9856-22H); * IBM Power System L1124 (9856-42H); * IBM Power System E1150 (9043-MRU); Customers with the products below should install FW1120.02(1120_195), or newer to remediate this vulnerability. | Update reference ↗ |
| CVE-2026-18870 | 24 Sep 2026 | PowerVM Hypervisor: FW1120.00 ≤ FW1120.01, FW1110.00 ≤ FW1110.31, FW1060.00 ≤ FW1060.81, FW950.00 ≤ FW950.H3 | Customers with the products below should install FW1110.32(1110_138), FW1120.02(1120_171), or newer to remediate this vulnerability.; Power 11; * IBM Power System E1180 (9080-HEU); Customers with the products below should install FW1110.32(1110_160), FW1120.02(1120_195), or newer to remediate this vulnerability.; * IBM Power System S1122 (9824-22A); * IBM Power System S1124 (9824-42A); * IBM Power System S1122s (9824-22B); * IBM Power System S1114 (9824-41B); * IBM Power System L1122 (9856-22H); * IBM Power System L1124 (9856-42H); * IBM Power System E1150 (9043-MRU); Customers with the products below should install FW1120.02(1120_195), or newer to remediate this vulnerability. | Update reference ↗ |
| CVE-2026-17511 | 24 Sep 2026 | PowerVM Hypervisor: FW1120.00 ≤ FW1120.01, FW1110.00 ≤ FW1110.31, FW1060.00 ≤ FW1060.81, FW950.00 ≤ FW950.H3 | Customers with the products below should install FW1110.32(1110_138), FW1120.02(1120_171), or newer to remediate this vulnerability.; Power 11; * IBM Power System E1180 (9080-HEU); Customers with the products below should install FW1110.32(1110_160), FW1120.02(1120_195), or newer to remediate this vulnerability.; * IBM Power System S1122 (9824-22A); * IBM Power System S1124 (9824-42A); * IBM Power System S1122s (9824-22B); * IBM Power System S1114 (9824-41B); * IBM Power System L1122 (9856-22H); * IBM Power System L1124 (9856-42H); * IBM Power System E1150 (9043-MRU); Customers with the products below should install FW1120.02(1120_195), or newer to remediate this vulnerability. | Update reference ↗ |
| CVE-2026-17504 | 24 Sep 2026 | PowerVM Hypervisor: FW1120.00 ≤ FW1120.01, FW1110.00 ≤ FW1110.31, FW1060.00 ≤ FW1060.81, FW950.00 ≤ FW950.H3 | Customers with the products below should install FW1110.32(1110_138), FW1120.02(1120_171), or newer to remediate this vulnerability.; Power 11; * IBM Power System E1180 (9080-HEU); Customers with the products below should install FW1110.32(1110_160), FW1120.02(1120_195), or newer to remediate this vulnerability.; * IBM Power System S1122 (9824-22A); * IBM Power System S1124 (9824-42A); * IBM Power System S1122s (9824-22B); * IBM Power System S1114 (9824-41B); * IBM Power System L1122 (9856-22H); * IBM Power System L1124 (9856-42H); * IBM Power System E1150 (9043-MRU); Customers with the products below should install FW1120.02(1120_195), or newer to remediate this vulnerability. | Update reference ↗ |
| CVE-2026-17503 | 24 Sep 2026 | PowerVM Hypervisor: FW1120.00 ≤ FW1120.01, FW1110.00 ≤ FW1110.31, FW1060.00 ≤ FW1060.81, FW950.00 ≤ FW950.H3 | Customers with the products below should install FW1110.32(1110_138), FW1120.02(1120_171), or newer to remediate this vulnerability.; Power 11; * IBM Power System E1180 (9080-HEU); Customers with the products below should install FW1110.32(1110_160), FW1120.02(1120_195), or newer to remediate this vulnerability.; * IBM Power System S1122 (9824-22A); * IBM Power System S1124 (9824-42A); * IBM Power System S1122s (9824-22B); * IBM Power System S1114 (9824-41B); * IBM Power System L1122 (9856-22H); * IBM Power System L1124 (9856-42H); * IBM Power System E1150 (9043-MRU); Customers with the products below should install FW1120.02(1120_195), or newer to remediate this vulnerability. | Update reference ↗ |
| CVE-2026-17413 | 24 Sep 2026 | PowerVM Hypervisor: FW1120.00 ≤ FW1120.01, FW1110.00 ≤ FW1110.31, FW1060.00 ≤ FW1060.81, FW950.00 ≤ FW950.H3 | Customers with the products below should install FW1110.32(1110_138), FW1120.02(1120_171), or newer to remediate this vulnerability.; Power 11; * IBM Power System E1180 (9080-HEU); Customers with the products below should install FW1110.32(1110_160), FW1120.02(1120_195), or newer to remediate this vulnerability.; * IBM Power System S1122 (9824-22A); * IBM Power System S1124 (9824-42A); * IBM Power System S1122s (9824-22B); * IBM Power System S1114 (9824-41B); * IBM Power System L1122 (9856-22H); * IBM Power System L1124 (9856-42H); * IBM Power System E1150 (9043-MRU); Customers with the products below should install FW1120.02(1120_195), or newer to remediate this vulnerability. | Update reference ↗ |
| CVE-2026-4936 | 19 Aug 2026 | FW1110.00 ≤ FW1110.20; FW1060.00 ≤ FW1060.71; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-4937 | 19 Aug 2026 | FW1110.00 ≤ FW1110.20; FW1060.00 ≤ FW1060.71; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-16707 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-17028 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-17091 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-17097 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-18821 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-18871 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-17414 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-16661 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80; FW950.00 ≤ FW950.H2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-15961 | 19 Aug 2026 | FW1120.00; FW1110.00 ≤ FW1110.30; FW1060.00 ≤ FW1060.80 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-11885 | 30 Jul 2026 | FW1110.00 ≤ FW1110.20; FW1060.00 ≤ FW1060.71; FW950.00 ≤ FW950.H1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-4932 | 28 Jul 2026 | FW1110.00 ≤ FW1110.20; FW1060.00 ≤ FW1060.71 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36194 | 2 Feb 2026 | FW1110.00 ≤ FW1110.03; FW1060.00 ≤ FW1060.51; FW950.00 ≤ FW950.F0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36238 | 2 Feb 2026 | FW1110.00 ≤ FW1110.03; FW1060.00 ≤ FW1060.51; FW950.00 ≤ FW950.F0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-36035 | 14 Sep 2025 | FW950.00 ≤ FW950.E0; FW1050.00 ≤ FW1050.50; FW1060.00 ≤ FW1060.40 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-0986 | 28 Mar 2025 | FW1050.00 ≤ FW1050.30; FW1060.00 ≤ FW1060.20 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-41781 | 22 Nov 2024 | FW950.00 ≤ FW950.90; FW1030.00 ≤ FW1030.60; FW1050.00 ≤ FW1050.20; FW1060.00 ≤ FW1060.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-46183 | 6 Feb 2024 | FW950.00 ≤ FW950.90; FW1020.00 ≤ FW1020.40; FW1030.00 ≤ FW1030.30 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-33851 | 4 Feb 2024 | FW950.00 ≤ FW950.90; FW1020.00 ≤ FW1020.40; FW1030.00 ≤ FW1030.30 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-25683 | 15 Jun 2023 | FW950.00 ≤ FW950.71; FW1010.00 ≤ FW1010.40; FW1020.00 ≤ FW1020.20; FW1030.00 ≤ FW1030.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-30440 | 23 May 2023 | FW860.00 ≤ FW860.B3; FW950.00 ≤ FW950.70; FW1010.00 ≤ FW1010.50; FW1020.00 ≤ FW1020.30; FW1030.00 ≤ FW1030.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-30438 | 17 May 2023 | FW950.00 ≤ FW950.70; FW1010.00 ≤ FW1010.50; FW1020.00 ≤ FW1020.30; FW1030.00 ≤ FW1030.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-22445 | 18 Jul 2022 | FW1010; FW950 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-38918 | 5 Jan 2022 | FW940; FW950; FW860; FW1010 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-38937 | 10 Dec 2021 | FW940; FW950; FW1010 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-38917 | 10 Dec 2021 | FW940; FW950; FW860 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-38923 | 6 Oct 2021 | FW1010 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-29795 | 21 Sep 2021 | FW930; FW940; FW950; FW860 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-29765 | 4 Aug 2021 | FW940; FW950 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20505 | 29 Jul 2021 | FW920; FW930; FW940; FW950 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.