Skip to main content

IBM i CVE-2026-18150

| EUVDEUVD-2026-57530 MEDIUM
Race Condition (CWE-362)
2026-08-12 ibm GHSA-mxq4-3vpv-f9jh
5.3
CVSS 3.1 · NVD
View

Attack ChainAIDerived

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

  1. Access
    Obtain valid low-privilege IBM i credentials
  2. Delivery
    Authenticate remotely over network
  3. Exploit
    Identify and trigger the vulnerable operation
  4. Execution
    Exploit race condition timing window
  5. Impact
    Read out-of-scope sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

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

Exploitation Conditions

Exploitation requires a valid low-privilege IBM i user account (CVSS PR:L confirmed) - unauthenticated exploitation is not possible. The attack is delivered over the network (AV:N) without requiring any victim user interaction (UI:N). The vulnerable system must be running IBM i version 7.3, 7.4, 7.5, or 7.6. The specific subsystem, API, or feature involved in the race condition is not disclosed in the available vendor data, meaning defenders cannot selectively disable a single feature as a targeted workaround. Key limiting factors: mandatory authentication (PR:L) eliminates internet-scale unauthenticated attack scenarios; impact is read-only with no code execution or integrity path; and no public exploit code exists to lower the technical barrier.

Impact

The vendor-assigned CVSS base score of 4.3 (Medium) appropriately reflects the constrained impact ceiling: only confidentiality is affected (C:L), with no integrity or availability impact (I:N, A:N), and exploitation requires authenticated network access (PR:L, AV:N). The AC:L assignment warrants scrutiny - race conditions (CWE-362) inherently involve timing dependencies, and low complexity may indicate a wide or reliably triggerable race window rather than a trivial exploit; defenders should not assume this is trivially exploitable simply because AC:L is assigned. No EPSS score was provided in the source data, so probabilistic exploitation likelihood cannot be quantified. The vulnerability is not listed in the CISA KEV catalog, and no public exploit code has been identified, together indicating no confirmed or widespread active exploitation. The impact is bounded: an attacker can read some sensitive data but cannot modify the system or cause an outage. Given this profile, standard patching cadence is appropriate - this does not warrant emergency response, though organizations running IBM i in regulated industries (finance, healthcare) where data confidentiality is paramount should prioritize the patch due to the information disclosure nature of the flaw.

Exploit ScenarioDerived

An attacker holding any valid low-privilege IBM i user account authenticates remotely over the network and repeatedly triggers the vulnerable operation to win a race condition timing window, reading sensitive data - such as configuration values, credentials, or business records - that their privilege level should not permit. Because no public exploit code has been identified, a would-be attacker must independently discover or reconstruct the race condition trigger, raising the practical bar above the AC:L CVSS rating implies.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Aug 12, 2026

IBM i versions 7.3 through 7.6 expose sensitive information to remote authenticated attackers via a race condition (CWE-362). The flaw allows a low-privileged network-authenticated user to read data outside their authorization boundary during a timing window in an undisclosed subsystem. Vendor-released patch is available; no public exploit code exists and the vulnerability is not listed in CISA KEV.

RemediationAI

Apply the vendor-released patch documented in IBM support page 7283292 at https://www.ibm.com/support/pages/node/7283292. The exact patched version numbers for each affected release (7.3, 7.4, 7.5, 7.6) must be confirmed directly from the IBM advisory, as the available intelligence does not specify the precise fix versions. If immediate patching is not feasible, reduce exposure by restricting network access to IBM i systems via firewall policy so that only authorized hosts and users can authenticate - this does not eliminate the vulnerability but shrinks the attacker population to already-credentialed insiders. Additionally, review and enforce least-privilege principles for IBM i user profiles to limit the accounts that could be used as a stepping stone, noting that this mitigation does not close the race condition itself.

Affected VersionsENISA

i 7.6
i 7.3
i 7.4
i 7.5

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 (successor to AS/400 and iSeries) is an integrated operating system for IBM Power Systems, widely deployed in enterprise environments for ERP, banking, and manufacturing workloads. CWE-362 (Race Condition / Concurrent Execution Using Shared Resource with Improper Synchronization) indicates a time-of-check to time-of-use (TOCTOU) or similar timing flaw where a shared resource is briefly accessible in an unprotected state between two sequential operations. The CVSS vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N confirms the attack is network-delivered, requires low-privilege credentials, no user interaction, and yields only partial confidentiality impact with no integrity or availability consequence. The CPE cpe:2.3:a:ibm:i:*:*:*:*:*:*:*:* covers all minor versions of IBM i across the stated major releases.

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 MEDIUM
NVD 5.3 MEDIUM
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 3.1 LOW

Race conditions (CWE-362) require timing precision to win the window, justifying AC:H over vendor-assigned AC:L; PR:L reflects mandatory authentication; C:L/I:N/A:N matches the information-disclosure-only impact.

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

Primary rating from Vendor (ibm).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

1
CVSS changed
Aug 17, 2026 - 17:52 NVD
4.3 (MEDIUM) 5.3 (MEDIUM)

DescriptionNVD

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to obtain sensitive information due to a race condition.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
enterprise AS/400 successor, concentrated in banking, manufacturing, and government
Data Quality
5 sources
Confidence: Medium

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).

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