Memory disclosure and service interruption via buffer overflow
Published Oct 6, 2026 · Updated Oct 6, 2026
Buffer overflow in HPE AOS-Switch 16.11.0000 through 16.11.0031 allows remote attackers to expose device memory or interrupt service. HPE identifies an affected interface but does not disclose its protocol, input field, or the buffer operation responsible for the overflow. Exploitation requires network reachability but no authentication or user interaction; the reported denial of service has no specified crash, hang, or reboot mode.
Summary
What happened
Buffer overflow in HPE AOS-Switch 16.11.0000 through 16.11.0031 allows remote attackers to expose device memory or interrupt service. HPE identifies an affected interface but does not disclose its protocol, input field, or the buffer operation responsible for the overflow. Exploitation requires network reachability but no authentication or user interaction; the reported denial of service has no specified crash, hang, or reboot mode.
The record
- CVE
- CVE-2026-76747
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- Hewlett Packard Enterprise (HPE)
- Product
- AOS-Switch
- Classifications
- T1499
- Attack vector
- network
- 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
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