criticalOther

IBM i High-Authority Thread Privilege Escalation

First seen Aug 14, 2026 · Updated Aug 14, 2026 · CVSS 9.6

IBM-iprivilege-escalationauthorization-flawenterprise-serverinsider-threat

A critical vulnerability in IBM i affects versions 7.3 through 7.6, allowing a remote authenticated attacker to escalate privileges through improper authorization checks on high-authority threads. With a CVSS score of 9.6, this flaw could enable an attacker with low-level access to gain full administrative control over the system.

Technical Analysis

CVE-2026-17276 stems from improper authorization enforcement in IBM i's handling of high-authority threads, likely allowing a low-privileged authenticated user to inject or hijack execution context within threads running under elevated authority (such as *SECOFR or *ALLOBJ profiles). This class of flaw typically involves race conditions or missing authority validation checks during thread creation, switching, or job attribute inheritance, enabling privilege escalation without requiring memory corruption or code execution exploits. The remote and authenticated nature of the attack vector suggests exploitation via standard IBM i interfaces such as 5250 terminal sessions, ODBC/JDBC connections, or Db2 for i stored procedures. Given IBM i's prevalence as a backend ERP, database, and business logic host in finance, manufacturing, and government sectors, successful exploitation could lead to full system compromise, data exfiltration, or lateral movement into connected networks. If AI agents or automation pipelines interface with IBM i systems via database connectors, RPA tools, or API gateways for tasks like inventory queries or transaction processing, a privilege escalation here could allow attackers to manipulate agent-fed data or hijack service credentials used for those integrations.

Affected Systems

IBM i operating system versions 7.3, 7.4, 7.5, and 7.6; systems with multi-threaded jobs utilizing high-authority (e.g., *SECOFR-level) thread contexts; environments exposing IBM i via network-based authenticated access (TCP/IP host servers, Db2 for i connections, 5250 emulation)

Indicators of Compromise

  • No public IOCs available at this time; monitor IBM i audit journals (QAUDJRN) for unexpected QSYS or *SECOFR authority swaps, anomalous job/thread creation under elevated user profiles, and unusual use of system APIs related to thread/job attribute manipulation

Remediation Steps

  1. 1

    Apply IBM PTF Patches

    Immediately apply the relevant IBM i PTF (Program Temporary Fix) for CVE-2026-17276 as released by IBM for each affected release (7.3-7.6).

  2. 2

    Restrict Authenticated Access

    Limit which user profiles can establish remote authenticated sessions and enforce least-privilege authority on all non-administrative accounts.

  3. 3

    Enable Enhanced Auditing

    Configure QAUDJRN and related audit journals to log thread and job authority changes, and set alerts for anomalous escalation patterns.

  4. 4

    Review High-Authority Profiles

    Audit all *SECOFR and *ALLOBJ profile assignments and thread-level authority usage to reduce the attack surface for exploitation.

  5. 5

    Network Segmentation

    Restrict network exposure of IBM i host servers and database connection endpoints to trusted internal segments or VPN-only access.

CVE / Advisory IDs

CVE-2026-17276

Industries Most Exposed

financemanufacturinggovernmentretaillogisticshealthcare

Sources

Respond to this threat

Pro subscribers get a full AI-generated incident-response playbook for this threat — detection, containment, eradication, and recovery steps — plus an unlimited AI Threat Advisor for questions about your environment.