Skip to main content

IBM i CVE-2026-17029

| EUVDEUVD-2026-58386 HIGH
Out-of-bounds Write (CWE-787)
2026-08-13 ibm GHSA-wffc-v42m-c6j8
8.8
CVSS 3.1 · Vendor: ibm
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged IBM i local account
  2. Delivery
    Identify and invoke vulnerable system component
  3. Exploit
    Submit crafted input triggering out-of-bounds write
  4. Execution
    Corrupt adjacent memory or control structures in privileged context
  5. Persist
    Execute arbitrary code with elevated privileges
  6. Impact
    Full system compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The CVSS vector AV:L/PR:L confirms exploitation requires an active local session on the IBM i system with at minimum a low-privileged user account - remote unauthenticated exploitation is not possible. The specific component, feature, or configuration setting that must be invoked to trigger the out-of-bounds write is not named in the available description or advisory excerpt. No user interaction from a third party is required (UI:N), and attack complexity is low (AC:L), meaning no race conditions or special environmental states are needed beyond possessing a valid low-privilege local account and executing the triggering action. The scope change (S:C) implies the vulnerable component runs under a higher-privileged identity than the attacker's account. Limiting factors for exploitation: local access to the IBM i system is mandatory; IBM i systems are typically not exposed to general user populations and are often physically or network-segregated in enterprise deployments.

Impact

The CVSS 8.8 score is driven by AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - meaning a low-privileged local user, with no complexity barriers and no user interaction required, can trigger the flaw and escape their security context entirely. The scope change (S:C) is the critical amplifier: it indicates the vulnerable component executes in a separate, likely more privileged, security domain than the attacker's initial foothold, resulting in full triad impact. No EPSS score was provided, preventing probabilistic exploitation likelihood assessment. This vulnerability is not listed in the CISA KEV catalog based on available data, and no public exploit has been identified at time of analysis. Real-world risk is bounded by the requirement for local interactive access to an IBM i system - these are typically hardened, backend enterprise platforms with tightly controlled user access, limiting the attacker population. However, insider threat scenarios and post-compromise lateral movement from an already-compromised network make local privilege escalation on IBM i highly impactful given the sensitive business data these systems typically host.

Exploit ScenarioDerived

A low-privileged user with an active local session on an IBM i system crafts a malformed input or invokes a vulnerable system call targeting the affected component, triggering an out-of-bounds write that corrupts adjacent memory. The corruption overwrites a control structure such as a return address or function pointer within a higher-privileged process (consistent with S:C scope change), redirecting execution to attacker-supplied code. The attacker achieves arbitrary code execution in the elevated security context, gaining full control over the IBM i environment with high confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 13, 2026

Out-of-bounds write in IBM i 7.3 through 7.6 enables a local low-privileged attacker to execute arbitrary code, with scope change (S:C) indicating the exploit crosses a security boundary into a higher-privileged component - achieving full confidentiality, integrity, and availability impact. The CVSS score of 8.8 reflects the severity of privilege escalation potential despite requiring local access. No public exploit has been identified at time of analysis, and IBM has released a patch via their support portal.

RemediationAI

Apply the vendor-released patch per IBM's official advisory at https://www.ibm.com/support/pages/node/7283285 for all affected IBM i releases (7.3, 7.4, 7.5, 7.6). Exact PTF identifiers and installation instructions are detailed in that advisory. A patched version number was not independently confirmed from the available data - consult the advisory directly for specific fix levels. If immediate patching is not feasible, reduce exposure by restricting interactive local logon and command-line access to IBM i systems to only essential administrative personnel, noting that this may impact legitimate operator workflows. Audit and minimize low-privileged user accounts that have shell or command execution capabilities on IBM i, as PR:L indicates a standard user account is sufficient to trigger the flaw. Monitor IBM i system logs for anomalous privilege escalation events as a detective compensating control.

Affected VersionsENISA

i 7.5
i 7.4
i 7.3
i 7.6

Affected Packages

euvd i no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

IBM i (formerly AS/400, iSeries, System i) is IBM's proprietary integrated operating environment running on IBM Power Systems hardware, widely used by large enterprises for mission-critical business workloads. The vulnerability is classified as CWE-787 (Out-of-Bounds Write), a memory corruption class where a program writes data past the boundary of an allocated buffer, potentially overwriting adjacent memory regions including return addresses, function pointers, or control structures. This corruption can redirect execution flow to attacker-controlled code. The CPE cpe:2.3:a:ibm:i:*:*:*:*:*:*:*:* covers all sub-versions of IBM i across the four major releases (7.3, 7.4, 7.5, 7.6). The specific subsystem or component containing the vulnerable code path is not identified in available data.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ibm) PRIMARY 8.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Local low-privilege access sufficient (AV:L/PR:L); scope change warranted by execution in a higher-privileged component; arbitrary code execution yields full C/I/A impact.

3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a local attacker to execute arbitrary code due to an out-of-bounds write.

Executive ViewAI

Why It Matters

CVE-2026-17029 affects IBM i systems versions 7.3 through 7.6 and allows users with basic system access to gain administrative control and fully compromise affected systems. This escalation vulnerability puts business-critical applications, databases, and customer data at risk of unauthorized access, modification, or destruction. Organizations running IBM i in production should prioritize immediate patching to prevent potential loss of system control and operational continuity.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
legacy enterprise platform limited to IBM Power Systems customers
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy