VulnerabilityPublished 31 Jul 2025

CVE-2025-37111: Hewlett Packard Enterprise HPE Telco Network Function Virtual Orchestrator · Use of Hard-coded Credentials

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 26 Oct 2026, 12:55 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 4% 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

European organizations should implement the following specific mitigations: 1) Immediately audit all HPE Telco Network Function Virtual Orchestrator deployments to identify affected versions (7.0.0). 2) Restrict and monitor access to systems running the orchestrator, ensuring that only trusted administrators have high privilege local access. 3) Employ strict access control policies and multi-factor authentication for administrative accounts to reduce the risk of privilege misuse. 4) Use network segmentation and isolation to limit lateral movement in case of compromise. 5) Monitor logs and system behavior for unusual access patterns or attempts to retrieve authentication keys. 6) Engage with HPE support channels to obtain patches or workarounds as they become available and apply them promptly. 7) Consider implementing compensating controls such as credential rotation, if supported, or additional encryption layers around stored keys. 8) Conduct regular security training and awareness for administrators to recognize and prevent misuse of privileged access. These steps go beyond generic advice by focusing on access restriction, monitoring, and proactive engagement with the vendor for patching.

Description

A vulnerability was discovered in the storage policy for certain sets of authentication keys 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, particularly telecommunications providers and network operators using HPE Telco Network Function Virtual Orchestrator, this vulnerability poses a significant risk to the confidentiality of sensitive system information. Unauthorized access to authentication keys could allow attackers to gain insights into network configurations, orchestrator operations, or potentially pivot to other network components. Given the critical role of NFV orchestrators in managing virtualized network functions, any compromise could disrupt service management and degrade trust in network integrity. Although the vulnerability requires local high-privilege access, insider threats or attackers who have already breached perimeter defenses could exploit it to escalate access or extract sensitive data. This could lead to regulatory compliance issues under GDPR if personal data or critical infrastructure information is exposed. Additionally, the telecommunications sector is a strategic asset in Europe, and disruptions or breaches could have broader national security implications.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (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:02 UTC

WeaknessesCWE-798

Technical details

References

Community reviews

Related threats