Adjacent memory disclosure and service interruption
Published Oct 6, 2026 · Updated Oct 6, 2026
Buffer overflow in HPE AOS-Switch 16.11.0000 through 16.11.0031 allows attackers to expose sensitive memory and interrupt service via adjacent-network access. HPE has not disclosed the affected component or the buffer operation that mishandles untrusted input. No credentials or user interaction are required, but the attacker must be network-adjacent; the service-interruption failure mode is unspecified.
Summary
What happened
Buffer overflow in HPE AOS-Switch 16.11.0000 through 16.11.0031 allows attackers to expose sensitive memory and interrupt service via adjacent-network access. HPE has not disclosed the affected component or the buffer operation that mishandles untrusted input. No credentials or user interaction are required, but the attacker must be network-adjacent; the service-interruption failure mode is unspecified.
The record
- CVE
- CVE-2026-76746
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- Hewlett Packard Enterprise (HPE)
- Product
- AOS-Switch
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 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=16.11.0000 <=16.11.0031
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.
Weakness, pattern, technique
No sourced classifications are available.
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