Security Resilience

CVE-2026-17121

DoS in Ibm Vios 4.1.0 – 4.1.0.50

Published
20 August 2026
Modified
27 October 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0055 46th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-17121 is a high-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Ibm Vios. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to uncontrolled recursion.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-16836Same product: Ibm Vios
CVE-2026-16831Same product: Ibm Vios
CVE-2026-16837Same product: Ibm Vios
CVE-2026-16818Same product: Ibm Vios
CVE-2026-19446Same product: Ibm Vios
CVE-2026-16690Same product: Ibm Vios
CVE-2026-16824Same product: Ibm Vios
CVE-2023-45167Same product: Ibm Vios
CVE-2023-45171Same product: Ibm Vios
CVE-2025-36236Same product: Ibm Vios

Affected Assets

ibm
vios
4.1.0 — 4.1.0.50 · 4.1.1.0 — 4.1.1.30 · 4.1.2.0 — 4.1.2.20
ibm
aix
7.2.5 — 7.2.5.212 · 7.3.2 — 7.3.2.5 · 7.3.3 — 7.3.3.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

SC-5 directly limits the effects of resource-exhaustion events that constitute uncontrolled consumption.

SC-6 enforces explicit allocation limits on resources, structurally preventing the weakness from occurring.

Process isolation confines resource consumption to separate domains, reducing blast radius without stopping the root flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

finds

Security testing in development can detect excessive recursion via static analysis or fuzzing.

finds

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

blocks

Monitoring network service usage and applying controls to restrict access when necessary limits an attacker’s ability to consume excessive resources through unrestricted or unauthenticated service calls.

prevents

Secure coding standards directly prohibit or constrain recursive constructs that could exhaust stack or memory.

finds

Capacity management includes monitoring and limits that mitigate resource exhaustion from runaway recursion.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-400, a class-level weakness. Rules are authored against its narrower children: CWE-770.
  • No fine-grained STIG row for CWE-674, a class-level weakness, and none of its children carries one either.

References