Adjacent-memory overwrite via integer-underflowed bounds check
Published Aug 19, 2026 · Updated Aug 20, 2026
Heap-based buffer overflow in IBM's integrated platform versions 7.3 through 7.6 allows remote authenticated users to overwrite adjacent memory. An integer underflow in an undisclosed bounds-checking locus causes the check to accept a size that permits writes beyond the intended heap buffer. A low-privileged account and a high-complexity trigger are required; IBM reports limited memory integrity impact and no confidentiality or availability impact.
Summary
What happened
Heap-based buffer overflow in IBM's integrated platform versions 7.3 through 7.6 allows remote authenticated users to overwrite adjacent memory. An integer underflow in an undisclosed bounds-checking locus causes the check to accept a size that permits writes beyond the intended heap buffer. A low-privileged account and a high-complexity trigger are required; IBM reports limited memory integrity impact and no confidentiality or availability impact.
The record
- CVE
- CVE-2026-18102
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- IBM
- Product
- IBM i
- Classifications
- CWE-122
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.3
- Affected versionversion=7.4
- Affected versionversion=7.5
- Affected versionversion=7.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo