VulnerabilityPublished 14 Aug 2025

CVE-2025-36581: Dell PowerEdge · Access of Memory Location After End of Buffer

Affects Dell PowerEdgeSource CVE Database V5

Not known to be exploited · CVSS 3.8 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

3.8Low

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:L/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
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: 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: 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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 Aug 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
Dell PowerEdge	Affected <=1.25.0	Fixed in–

AI-suggested

Given the vulnerability resides in BIOS firmware, mitigation should focus on the following specific actions: 1) Monitor Dell's official security advisories closely for the release of BIOS updates or patches addressing CVE-2025-36581 and apply them promptly once available. 2) Restrict local access to Dell PowerEdge servers to trusted personnel only, employing strong physical security controls and access logging to prevent unauthorized presence. 3) Implement strict role-based access controls and limit administrative privileges to reduce the risk of low-privileged users exploiting the vulnerability. 4) Use endpoint detection and response (EDR) solutions to monitor for unusual local activity that could indicate attempts to exploit BIOS-level vulnerabilities. 5) Consider BIOS-level security features such as Secure Boot and BIOS password protection to prevent unauthorized firmware modifications. 6) Conduct regular security audits and penetration testing focusing on local privilege escalation vectors to identify and remediate potential attack paths. 7) Isolate critical servers in secure network segments to limit lateral movement opportunities if local access is compromised. These targeted measures go beyond generic advice by focusing on BIOS-specific controls, physical security, and monitoring strategies tailored to the nature of this vulnerability.

Description

Dell PowerEdge Platform version(s) 14G AMD BIOS v1.25.0 and prior, contain(s) an Access of Memory Location After End of Buffer vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Information exposure.

Impact

For European organizations, especially those relying on Dell PowerEdge 14G AMD servers, this vulnerability poses a risk primarily to confidentiality. Since the flaw allows low-privileged local attackers to access memory beyond intended boundaries, sensitive data such as cryptographic keys, passwords, or other critical information could be exposed. This is particularly concerning for data centers, cloud service providers, and enterprises handling sensitive or regulated data under GDPR. Although the vulnerability does not directly affect system integrity or availability, the exposure of confidential information could lead to further exploitation, including privilege escalation or targeted attacks. The requirement for local access limits the threat to insiders or attackers who have already compromised the network perimeter. However, in environments with shared access or weak physical security controls, the risk increases. The lack of known exploits reduces immediate risk but does not eliminate the potential for future exploitation. Organizations with compliance obligations must consider the implications of any data exposure resulting from this vulnerability.

CWE-788Access of Memory Location After End of Buffer (opens in a new tab)
Base weakness
The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
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)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

dell.com/support/kbdoc/en-us/000356405/dsa-2025-299-security-update-for-dell-poweredge-server-bios-for-an-access-of-memory-location-after-end-of-buffer-vulnerability (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Aug 2025, 14:18 UTC

WeaknessesCWE-788

Technical details

References

Community reviews

Related threats