CVE-2025-37110VulnerabilityPublished 31 Jul 2025

CVE-2025-37110: Hewlett Packard Enterprise HPE Telco Network Function Virtual Orchestrator · Insecure Storage of Sensitive Information

Affects Hewlett Packard Enterprise HPE Telco Network Function Virtual OrchestratorSource CVE Database V5

Not known to be exploited · CVSS 6.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.0Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 31 Jul 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 Telco Network Function Virtual Orchestrator	Affected =7.0.0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should prioritize the following actions: 1) Upgrade or patch the HPE Telco NFVO to a version where this vulnerability is addressed once HPE releases a fix. 2) Restrict and monitor local access to NFVO systems strictly, ensuring that only trusted, authorized personnel have high privilege access. Implement robust access controls and use multi-factor authentication for administrative accounts. 3) Conduct regular audits of stored credential information and system configurations to detect any anomalies or unauthorized access attempts. 4) Employ encryption for sensitive credential storage if supported by the product or through additional security layers, such as disk encryption or vault solutions, to reduce the risk of credential exposure. 5) Implement network segmentation to isolate NFVO systems from less trusted network zones, limiting the attack surface. 6) Enhance logging and monitoring to detect suspicious activities related to credential access or privilege escalation. 7) Train administrators on secure handling of credentials and the importance of minimizing local privileged access. These steps go beyond generic advice by focusing on compensating controls until a vendor patch is available and emphasizing operational security around privileged access and credential management.

Description

A vulnerability was discovered in the storage policy for certain sets of sensitive credential information in the HPE Telco Network Function Virtual Orchestrator. Successful Exploitation could lead to unauthorized parties gaining access to sensitive system information.

Impact

For European organizations, especially telecommunications providers and service operators using HPE Telco NFVO version 7.0.0, this vulnerability poses a significant risk to the confidentiality of sensitive credentials. Unauthorized access to these credentials could allow attackers or malicious insiders to manipulate network function orchestration, potentially leading to unauthorized configuration changes, interception of network traffic, or disruption of virtual network services. Given the critical role of NFVOs in managing virtualized network functions, exploitation could undermine the security posture of telecom infrastructure, affecting service availability indirectly through misconfigurations or enabling further attacks. The confidentiality breach could also lead to regulatory compliance issues under GDPR, as sensitive operational data and credentials are involved. Although exploitation requires high privileges and local access, the changed scope and high confidentiality impact mean that once exploited, the attacker could escalate their control within the network environment. This is particularly concerning for European telecom operators who are key infrastructure providers and subject to stringent cybersecurity regulations.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw04891en_us (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Jul 2025, 20:03 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats