IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the PowerVM hypervisor call interface. An attacker with root access to a guest partition can issue a specially crafted hypervisor call to inject an arbitrary amount of data into hypervisor or partition memory, resulting in either a crash causing a full platform re-IPL and terminating all hosted partitions, or corruption of hypervisor or partition memory. The PowerVM hypervisor will restart automatically; however, repeated exploitation could result in a sustained availability impact. Successful exploitation results in an integrity and availability impact to the managed system.
CVE-2026-17091
Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. a secondary CVSS source baseline 8.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 8.4(high)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity84% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (1)
Auto-updated Aug 19, 2026Security Bulletin: This Power System update is being released to address CVE-2026-17091
https://www.ibm.com/support/pages/node/7283229Vendor Advisories for CVE-2026-17091(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× 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.
- 2026-08-21 04:51 UTCEG score recompute
- 2026-08-21 04:51 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 16:36 UTCEG score recompute
- 2026-08-20 16:36 UTCGHSA enrichment
- 2026-08-20 16:07 UTCEG score recompute
- 2026-08-20 16:07 UTCGHSA enrichment
- 2026-08-20 13:25 UTCGHSA enrichment
- 2026-08-20 08:33 UTCEG score recompute
- 2026-08-20 08:33 UTCGHSA enrichment
- 2026-08-19 20:19 UTCEG score recompute
- 2026-08-19 19:58 UTCEG score recompute
- 2026-08-19 19:57 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-17091?
When was CVE-2026-17091 disclosed?
Is CVE-2026-17091 actively exploited?
What is the CVSS score of CVE-2026-17091?
How do I remediate CVE-2026-17091?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-17091
Is Your Infrastructure Affected by CVE-2026-17091?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.