CVE-2025-37130VulnerabilityPublished 16 Sep 2025

CVE-2025-37130: Hewlett Packard Enterprise (HPE) HPE Aruba Networking EdgeConnect SD-WAN Gateway · Exposed Files or Directories

Affects Hewlett Packard Enterprise (HPE) HPE Aruba Networking EdgeConnect SD-WAN GatewaySource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Hewlett Packard Enterprise (HPE) HPE Aruba Networking EdgeConnect SD-WAN Gateway	Affected =9.5.0.0 =9.4.0.0	Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Immediately audit and restrict CLI access to the EdgeConnect SD-WAN Gateway, ensuring that only trusted administrators with a strict need-to-know have authenticated access. Implement multi-factor authentication (MFA) for CLI access to reduce the risk of compromised credentials being exploited. 2) Monitor and log all CLI access and commands executed on the device to detect anomalous or unauthorized file access attempts. 3) Apply network segmentation to isolate management interfaces of SD-WAN gateways from general network access, limiting exposure to potential attackers. 4) Engage with HPE support channels to obtain and apply security patches or firmware updates as soon as they become available. 5) Conduct regular vulnerability assessments and penetration testing focused on SD-WAN infrastructure to identify and remediate similar issues proactively. 6) Educate administrators about the risks of credential compromise and enforce strong password policies. 7) Consider deploying additional endpoint detection and response (EDR) solutions to monitor for lateral movement or unusual activity stemming from compromised SD-WAN devices.

Description

A vulnerability in the command-line interface of EdgeConnect SD-WAN could allow an authenticated attacker to read arbitrary files within the system. Successful exploitation could allow an attacker to read sensitive data from the underlying file system.

Impact

For European organizations, this vulnerability poses a significant risk, especially for enterprises and service providers relying on HPE Aruba EdgeConnect SD-WAN Gateways to manage their wide-area networks. The ability to read arbitrary files can expose sensitive configuration data, authentication credentials, or cryptographic keys, which could be leveraged to escalate privileges or conduct further attacks such as network interception or disruption. Given the critical role of SD-WAN in ensuring secure and reliable connectivity across distributed sites, exploitation could undermine network confidentiality and trust. This is particularly impactful for sectors with stringent data protection requirements under GDPR, such as finance, healthcare, and government agencies. The exposure of sensitive data could lead to regulatory penalties, reputational damage, and operational disruptions. Additionally, the medium severity and requirement for authenticated access mean that insider threats or compromised user accounts could be leveraged to exploit this vulnerability, increasing the risk profile for organizations with less stringent access controls or monitoring.

CWE-552Files or Directories Accessible to External Parties (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product makes files or directories accessible to unauthorized actors, even though they should not be.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.1 (opens in a new tab)
V12.4.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
Attack patterns
Collect Data from Common Resource Locations (opens in a new tab)
Probe System Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw04943en_us&docLocale=en_US (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Sep 2025, 01:13 UTC

WeaknessesCWE-552

Technical details

References

Community reviews

Related threats