CVE-2025-36581
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDell 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDell PowerEdge 14G AMD BIOS versions 1.25.0 and prior contain a memory safety vulnerability where the system accesses memory locations beyond the end of a buffer. A low-privileged local attacker could exploit this to read sensitive information from memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.26.0< 1.26.0< 1.26.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the exact PowerEdge modelRun 'dmidecode -s system-product-name' or check the system label to confirm the model is R7425, R7415, or R6415Affected if Model is not one of these three, the system is not affected by this specific CVE
-
Check the current BIOS firmware versionRun 'dmidecode -s bios-version' or access the BIOS setup (F2 during boot) to view the BIOS version under the Main or Information tabAffected if Cannot retrieve a version number, verify you have appropriate system access
-
For R7425: check if version <= 1.26.0. For R7415 and R6415: check if version < 1.26.0. Note that version 1.25.0 and prior are definitively affectedAffected if Your BIOS version falls within the affected range for your specific model
Your system is affected if it is a Dell PowerEdge R7425, R7415, or R6415 running BIOS firmware version 1.26.0 or lower (R7425) or below 1.26.0 (R7415/R6415).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.26.0
Update the Dell PowerEdge 14G AMD BIOS to a version newer than 1.25.0 to patch the buffer over-read vulnerability.
BIOS firmware version 1.26.0 or later (confirm the latest available version from Dell for PowerEdge R7425/R7415/R6415)
- Identify the current BIOS firmware version on the affected PowerEdge system (R7425, R7415, or R6415) using the iDRAC web interface or BIOS setup utility
- Navigate to Dell support website (www.dell.com) and locate the BIOS update for your specific PowerEdge model
- Download the BIOS firmware version 1.26.0 or later (verify the exact latest version from Dell's support page for your model)
- Create a bootable USB drive with the BIOS update file following Dell's instructions, or upload the update via iDRAC web interface
- Apply the BIOS update by running the firmware update utility or rebooting into the BIOS update process
- Allow the update to complete and verify the new BIOS version is installed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36581 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data