Memory corruption via out-of-bounds write
Published Oct 15, 2026 · Updated Oct 15, 2026
An out-of-bounds write in HPE NonStop QIO Monitor allows remote authenticated users to corrupt buffer data over the network. The CNA record lists T8671L02^ABH and earlier but does not disclose the triggering input, affected code path, or incorrect bounds operation. Exploitation requires user interaction; the documented consequence is buffer corruption, not established arbitrary code execution.
Summary
What happened
An out-of-bounds write in HPE NonStop QIO Monitor allows remote authenticated users to corrupt buffer data over the network. The CNA record lists T8671L02^ABH and earlier but does not disclose the triggering input, affected code path, or incorrect bounds operation. Exploitation requires user interaction; the documented consequence is buffer corruption, not established arbitrary code execution.
The record
- CVE
- CVE-2026-76661
- Published
- Oct 15, 2026
- Updated
- Oct 15, 2026
- Vendor
- Hewlett Packard Enterprise
- Product
- HPE NonStop QIO Monitor
- Classifications
- CWE-20, CAPEC-456
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 15, 2026CVE publishedPublication date reported by the CVE source.
- Oct 15, 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=T8671L02^ABH and earlier
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started