Skip to main content

HPE VIA CVE-2026-95724

| EUVDEUVD-2026-116201 HIGH
2026-11-03 security-alert@hpe.com GHSA-9934-3x3p-7hrm
8.1
CVSS 3.1 · Vendor: hpe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain man-in-the-middle network position
  2. Delivery
    Victim VIA client initiates VPN connection
  3. Exploit
    Present fraudulent TLS certificate
  4. Execution
    Improper validation bypasses authentication
  5. Impact
    Intercept sensitive information

Vulnerability Assessment

Exploitation Conditions

Exploitation requires the HPE VIA client to establish a connection that the attacker can intercept, meaning the attacker needs a privileged network position (man-in-the-middle) between the client and the VPN gateway, and the victim client must initiate the connection (UI:R). The core precondition is the client's improper certificate validation, which lets a fraudulent certificate be accepted; the exact triggering configuration or client mode is not described in the available HPE advisory reference. Limiting factors: the required intercepting network position and the dependency on client-initiated connections constrain this below trivial remote mass exploitation, even though no authentication is needed (PR:N). Impact is limited to confidentiality and integrity (C:H/I:H); availability is not affected (A:N).

Impact

This is a credible this-week-priority issue rather than an inflated high-CVSS score, but it is not an emergency on current signals. The vendor-supplied CVSS of 8.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) reflects an unauthenticated, network-reachable improper certificate validation flaw with high confidentiality and integrity impact. The vuln.today Decision label is 'this_week', consistent with a serious but not actively-exploited flaw. No EPSS score, no CISA KEV listing, and no POC or exploit reference are present in the supplied data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. One internal tension to verify: the vendor vector pairs AV:N with AC:L and UI:R, yet certificate-validation bypasses typically require the attacker to occupy a man-in-the-middle position between the VIA client and its gateway, which usually raises attack complexity - this mechanism is not spelled out in the single HPE advisory reference, so the practical difficulty of exploitation should be confirmed with HPE. The absence of EPSS/KEV/POC is not an error; it simply means prioritization rests on the vendor vector and the 'this_week' decision label.

Exploit ScenarioDerived

An attacker positioned on the network path between an HPE VIA client and its VPN gateway presents a fraudulent or mismatched TLS certificate that the client fails to properly validate, allowing the attacker to impersonate the legitimate endpoint. Because authentication mechanisms can be bypassed, the attacker can intercept or obtain sensitive information (such as credentials or session data) once the victim's client connects. No public exploit code is identified at time of analysis; exploitation requires the victim client to initiate a connection (UI:R).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 03, 2026

Improper certificate validation in the HPE Networking Virtual Intranet Access (VIA) VPN client lets an unauthenticated attacker who can intercept client traffic present a fraudulent certificate, bypass authentication and reach sensitive information, with confidentiality and integrity both rated high. Exploitation is constrained rather than trivial: the attacker needs a man-in-the-middle position between client and VPN gateway, and the victim must initiate the connection (UI:R), which is why our assessment raises attack complexity to AC:H versus the published AC:L. There is no CISA KEV listing and no public exploit identified at time of analysis, making this a this-week priority rather than an emergency on current signals.

RemediationAI

The provided data contains no vendor-stated fix version, so patch status is not confirmed here; the authoritative remediation guidance is the HPE security bulletin hpesbnw05173en_us (https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05173en_us&docLocale=en_US), and administrators should obtain the corrected VIA client release from HPE and track the bulletin for the exact version and any stated workarounds. Exposure is governed by the assessed preconditions: the attacker must hold a man-in-the-middle position on the path between the VIA client and its gateway, and the user must initiate the connection, so tightening the network path and controlling which gateways clients connect to limits practical risk while the vendor fix is applied. No additional mitigations beyond the vendor's guidance can be confirmed from the supplied sources.

Affected VersionsENISA

Virtual Intranet Access (VIA) 0.0.0 ≤4.7.8

Affected Packages

euvd virtual_intranet_access_via no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw sits in the certificate validation logic the HPE VIA client applies when it establishes a connection to a VPN gateway. Because the client does not properly validate the certificate presented by the peer, a certificate supplied by an intercepting party can be accepted as legitimate, which undermines the authentication guarantee the TLS-style handshake is supposed to provide. The published description assigns no CWE; the flaw class is improper certificate validation (CWE-295 family). The supplied CPE data does not enumerate specific client builds, and the HPE advisory reference does not describe which client modes or configurations trigger the faulty validation path - the trigger is not described in the available sources. The CVSS vector in our assessment is AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N: no privileges are required, but the attacker must occupy an intercepting network position and the client user must initiate the connection; availability is unaffected.

Know when Hpe gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (hpe) PRIMARY 8.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
vuln.today AI 6.8 MEDIUM

Certificate-validation bypass realistically needs a man-in-the-middle position (AC:H) and a client-initiated connection (UI:R); no auth (PR:N); high confidentiality/integrity, no availability impact.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (hpe).

CVSS VectorVendor: hpe

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

An improper certificate validation vulnerability exists in HPE Networking Virtual Intranet Access (VIA). Successful exploitation could allow an unauthenticated remote attacker to bypass authentication mechanisms, leading to the possible disclosure of sensitive information.

Executive ViewAI

Why It Matters

The HPE Networking VIA VPN client contains a high-severity certificate validation flaw that could allow an attacker to intercept sensitive data when employees connect remotely. Successful exploitation requires a man-in-the-middle position and user action, but if achieved, it compromises confidentiality and integrity of VPN traffic, affecting remote workforce and potentially exposing proprietary information or credentials.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include enforcing strict certificate validation via client configuration, using trusted VPN gateways with certificate pinning, requiring VPN connections only over trusted networks (e.g., corporate-managed Wi-Fi or wired), implementing network monitoring to detect man-in-the-middle indicators, and enforcing multi-factor authentication to limit credential exposure.

Threat Intelligence Overview

Prevalence
Medium
enterprise VPN client (HPE/Aruba), common in corporate remote access but vendor-specific
Data Quality
2 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS N/A
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Hpe

View all
CVE-2017-5689 CRITICAL POC
9.8 May 02

An unprivileged network attacker could gain system privileges to provisioned Intel manageability SKUs: Intel Active Mana

CVE-2016-7434 HIGH POC
7.5 Jan 13

The read_mru_list function in NTP before 4.2.8p9 allows remote attackers to cause a denial of service (crash) via a craf

CVE-2026-76708 CRITICAL POC
9.8 Sep 22

Default, hard-coded credentials shipped on several administrative and system accounts in HPE's Analytics and Location En

CVE-2024-53676 CRITICAL POC
9.8 Nov 27

A directory traversal vulnerability in Hewlett Packard Enterprise Insight Remote Support may allow remote code execution

CVE-2022-37932 CRITICAL POC
9.8 Dec 12

A potential security vulnerability has been identified in Hewlett Packard Enterprise OfficeConnect 1820, 1850, and 1920S

CVE-2020-7136 CRITICAL POC
9.8 Apr 30

A security vulnerability in HPE Smart Update Manager (SUM) prior to version 8.5.6 could allow remote unauthorized access

CVE-2025-37097 HIGH POC
7.5 Jul 01

A vulnerability in HPE Insight Remote Support (IRS) prior to v7.15.0.646 may allow an unauthenticated denial of service

CVE-2019-8936 HIGH POC
7.5 May 15

NTP through 4.2.8p12 has a NULL Pointer Dereference. Rated high severity (CVSS 7.5), this vulnerability is remotely expl

CVE-2026-79849 CRITICAL
10.0 Oct 22

A maximum-severity, network-reachable flaw (CVSS 3.1 base 10.0) in an as-yet-unnamed HPE product allows remote attackers

CVE-2026-79848 CRITICAL
10.0 Oct 22

Unauthenticated network attackers can potentially achieve high confidentiality, integrity, and availability impact again

CVE-2026-79851 CRITICAL
10.0 Oct 22

HPE security bulletin hpesbnw05162en_us documents a maximum-severity (CVSS 10.0) exposure in an HPE product that is not

CVE-2026-79847 CRITICAL
10.0 Oct 22

HPE advisory hpesbnw05162en_us covers a product flaw carrying a CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy