Adjacent-network authentication bypass
Published Sep 29, 2026 · Updated Sep 29, 2026
Authentication bypass in HPE Networking Instant On APs through 3.4.1.0 allows remote attackers on adjacent networks to bypass access controls. HPE identifies the affected locus only as an AP management protocol and has not disclosed the message format or the authentication-check failure. Access requires an adjacent network position; a successful bypass can lead to elevated-privilege code execution on the device.
Summary
What happened
Authentication bypass in HPE Networking Instant On APs through 3.4.1.0 allows remote attackers on adjacent networks to bypass access controls. HPE identifies the affected locus only as an AP management protocol and has not disclosed the message format or the authentication-check failure. Access requires an adjacent network position; a successful bypass can lead to elevated-privilege code execution on the device.
The record
- CVE
- CVE-2026-76725
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- Hewlett Packard Enterprise (HPE)
- Product
- HPE Networking Instant On
- Classifications
- Unavailable
- Attack vector
- adjacent
- 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
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