Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid low-privilege IBM i credentials
-
DeliveryAuthenticate remotely over network
-
ExploitIdentify and trigger the vulnerable operation
-
ExecutionExploit race condition timing window
-
ImpactRead 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
Primary rating from Vendor (ibm).
CVSS VectorNVD
Lifecycle Timeline
1DescriptionNVD
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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).
EUVD-2026-57530
GHSA-mxq4-3vpv-f9jh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB