Sensitive-information disclosure and service interruption via kernel over-read
Published Aug 20, 2026 · Updated Aug 25, 2026
Kernel heap over-read in IBM AIX 7.2 and 7.3 and PowerVM VIOS 4.1 allows remote attackers to disclose data and interrupt service. IBM identifies the kernel heap as the locus but has not published the packet format, affected kernel routine, or bounds-checking error that causes the over-read. Remote attackers need only adjacent-network access and no credentials or user interaction; the read exposes sensitive memory and can make the system unavailable.
Summary
What happened
Kernel heap over-read in IBM AIX 7.2 and 7.3 and PowerVM VIOS 4.1 allows remote attackers to disclose data and interrupt service. IBM identifies the kernel heap as the locus but has not published the packet format, affected kernel routine, or bounds-checking error that causes the over-read. Remote attackers need only adjacent-network access and no credentials or user interaction; the read exposes sensitive memory and can make the system unavailable.
The record
- CVE
- CVE-2026-17060
- Published
- Aug 20, 2026
- Updated
- Aug 25, 2026
- Vendor
- IBM
- Product
- AIX
- Classifications
- CWE-200, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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.2
- Affected versionversion=7.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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