CVE-2025-37149VulnerabilityPublished 14 Oct 2025Updated 28 Oct 2025

CVE-2025-37149: Hewlett Packard Enterprise (HPE) ProLiant RL300 Gen11 Server · Vulnerability

Affects Hewlett Packard Enterprise (HPE) ProLiant RL300 Gen11 ServerSource CVE Database V5

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 06:26 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 14 Oct 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-26.

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) ProLiant RL300 Gen11 Server	Affected =0	Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Monitor Hewlett Packard Enterprise advisories closely and apply firmware updates or patches immediately once released to address CVE-2025-37149. 2) Restrict local administrative access to HPE ProLiant RL300 Gen11 Servers to trusted personnel only, using strong authentication and access controls to minimize the risk of privilege misuse. 3) Employ hardware-based security features such as TPM and secure boot to detect unauthorized firmware modifications. 4) Conduct regular firmware integrity checks and audits to identify anomalies or unauthorized changes. 5) Use network segmentation and endpoint detection to limit lateral movement if an attacker gains local access. 6) Implement strict logging and monitoring of privileged user activities on affected servers to detect suspicious behavior early. 7) Educate IT staff about the risks of firmware vulnerabilities and the importance of timely patching. These measures go beyond generic advice by focusing on access control, monitoring, and firmware integrity specific to the affected hardware.

Description

A potential out-of-bound reads vulnerability in HPE ProLiant RL300 Gen11 Server's UEFI firmware.

Impact

For European organizations, the confidentiality breach caused by this vulnerability could expose sensitive corporate or governmental data, cryptographic keys, or system configuration details stored in UEFI memory. This could facilitate further attacks such as privilege escalation, firmware manipulation, or persistent malware implantation. Organizations in sectors like finance, healthcare, government, and critical infrastructure that rely on HPE ProLiant RL300 Gen11 Servers are at heightened risk. The local access requirement limits the threat to insiders or attackers who have already compromised a system, but the potential for sensitive data exposure remains significant. The vulnerability does not affect system integrity or availability directly, so operational disruption is unlikely. However, the exposure of confidential data could lead to compliance violations under GDPR and other data protection regulations, resulting in legal and reputational damage. The lack of current exploits reduces immediate risk, but the medium severity rating and firmware-level nature of the flaw necessitate prompt attention.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hpe.com/hpesc/public/docDisplay?docId=hpesbhf04952en_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 28 Oct 2025, 21:28 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats