Unauthenticated code execution via interface buffer overflow
Published Sep 29, 2026 · Updated Sep 29, 2026
Buffer overflow in HPE Networking Instant On 3.4.1.0 and earlier allows remote attackers to execute privileged code via a device interface. HPE identifies an affected interface but has not disclosed the parser, input field, or operation that overruns the buffer. Exploitation requires network access to that interface but no authentication or user interaction; successful execution runs with privileged operating-system access.
Summary
What happened
Buffer overflow in HPE Networking Instant On 3.4.1.0 and earlier allows remote attackers to execute privileged code via a device interface. HPE identifies an affected interface but has not disclosed the parser, input field, or operation that overruns the buffer. Exploitation requires network access to that interface but no authentication or user interaction; successful execution runs with privileged operating-system access.
The record
- CVE
- CVE-2026-76721
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- Hewlett Packard Enterprise (HPE)
- Product
- HPE Networking Instant On
- Classifications
- T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 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=0.0.0.0 <=3.4.1.0
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