Vulnerability in Ibm RTAS firmware-to-OS interface (CVE-2026-17413, CVSS 5.1)

Summary

Vulnerability in Ibm RTAS firmware-to-OS interface (CVE-2026-17413). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

IBM PowerVM Hypervisor FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, FW1060.00 through FW1060.81, and FW950.00 through FW950.H3 is affected by a vulnerability in the RTAS firmware-to-OS interface. An attacker with administrator-level (root) access to a logical partition can send a specially crafted request to partition firmware, causing the partition to crash and become unavailable. Other partitions on the same managed system are not affected.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-17413 has been found in Ibm RTAS firmware-to-OS interface.
Risk of unauthorized operations or information disclosure. CVSS score: 5.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Ibm RTAS firmware-to-OS interface CVE-2026-17413" on the vendor's site.

CVE-2026-17413 (Ibm RTAS firmware-to-OS interface) — CWE-129 / CVSS v3 5.1
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-129) exists in Ibm RTAS firmware-to-OS interface.

📍 Affected scope

Check the vendor advisory for the affected versions of Ibm RTAS firmware-to-OS interface.

🔥 Severity

Severity: Medium (CVSS 5.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Ibm RTAS firmware-to-OS interface を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Summary

Original description

Auto-generated summary

Response actions

References