Skip to main content

IBM i CVE-2026-18511

| EUVDEUVD-2026-58470 HIGH
Out-of-bounds Write (CWE-787)
2026-08-13 ibm GHSA-7484-cp4g-hrj6
7.8
CVSS 3.1 · NVD
Share

Severity by source

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

Local authenticated low-privilege access required to reach JSSE; arbitrary code execution delivers full C/I/A; no scope change as impact is contained to JVM process.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/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:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

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

Lifecycle Timeline

5
Analysis Updated
Aug 17, 2026 - 13:43 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Aug 17, 2026 - 13:37 vuln.today
cvss_changed
CVSS changed
Aug 17, 2026 - 13:37 NVD
7.3 (HIGH) 7.8 (HIGH)
Analysis Generated
Aug 13, 2026 - 21:37 vuln.today
CVE Published
Aug 13, 2026 - 20:43 nvd
HIGH 7.3

DescriptionNVD

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a local authenticated attacker to generate a stack-based buffer overflow in the Native IBM i JSSE provider, caused by improper bounds checking during TLS session establishment. A local attacker could overflow a fixed-length buffer and execute arbitrary code on the system or cause the JVM process to crash.

AnalysisAI

Stack-based buffer overflow in the Native IBM i JSSE (Java Secure Socket Extension) provider enables local authenticated attackers with low privileges to execute arbitrary code or crash the JVM process on IBM i versions 7.3 through 7.6. The flaw is triggered during TLS session establishment via improper bounds checking against a fixed-length stack buffer. No public exploit or active exploitation has been identified at time of analysis - EPSS stands at 0.22% (12th percentile) and SSVC exploitation status is 'none' - but a vendor patch is available and should be applied given the high-impact code execution potential.

Technical ContextAI

IBM i (formerly OS/400) is IBM's integrated operating system for Power Systems hardware, widely used in enterprise environments such as banking and insurance. The Native IBM i JSSE provider is the platform's built-in Java TLS/SSL stack, used by Java applications running on IBM i to establish encrypted connections. CWE-787 (Out-of-bounds Write) identifies the root cause: during TLS session negotiation, the JSSE provider writes beyond the bounds of a fixed-length stack buffer due to absent or insufficient input length validation. This class of flaw typically arises when attacker-controlled data from the TLS handshake (e.g., session parameters or certificate fields) is copied into a statically allocated buffer without checking the source length. Affected products are identified under CPE cpe:2.3:a:ibm:i:*:*:*:*:*:*:*:* spanning versions 7.3, 7.4, 7.5, and 7.6.

RemediationAI

Apply the vendor-released patch documented in the IBM support advisory at https://www.ibm.com/support/pages/node/7283285; exact PTF identifiers for each IBM i release (7.3, 7.4, 7.5, 7.6) are detailed there and should be applied through the standard IBM i PTF process. A patched release version number was not independently confirmed in available data - administrators should reference the IBM advisory directly for the authoritative fix level. If immediate patching is not feasible, restrict local user privileges to limit which accounts can invoke Java applications using the Native JSSE provider, as PR:L is a prerequisite per the CVSS vector; this reduces attack surface but does not eliminate it and may impact application functionality. Additionally, monitoring for unexpected JVM process crashes (a signal of failed exploitation attempts) via IBM i system logs can provide early detection. No third-party workaround references are available; the IBM advisory is the sole authoritative source for fix details.

Share

CVE-2026-18511 vulnerability details – vuln.today

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