Cyber Resilience

CVE-2025-26482

Dell Idrac9 Firmware ≤ 7.00.00.181

Published
25 September 2025
Modified
16 January 2026
Patch / advisory
CVSS Score v3.1 4.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0029 21th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-26482 is a medium-severity Exposure of Sensitive System Information Due to Uncleared Debug Information (CWE-1258) vulnerability in Dell Idrac9 Firmware. Its CVSS base score is 4.9 (Medium).

Operationally, ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-17 (Remote Access) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Dell PowerEdge Server BIOS and Dell iDRAC9, all versions, contains an Information Disclosure vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Information Disclosure.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-0172Same product: Dell Dss 8440
CVE-2024-0154Same product: Dell Dss 8440
CVE-2024-0173Same product: Dell Dss 8440
CVE-2023-32460Same product: Dell Dss 8440
CVE-2024-0163Same product: Dell Emc Xc Core Xc450
CVE-2024-0162Same product: Dell Emc Xc Core Xc450
CVE-2023-32461Same product: Dell Emc Xc Core Xc450
CVE-2024-0161Same product: Dell Dss 8440
CVE-2024-38303Same product: Dell Dss 8440
CVE-2024-38304Same product: Dell Dss 8440

Affected Assets

dell
poweredge r770 firmware
≤ 1.2.6
dell
poweredge r670 firmware
≤ 1.2.6
dell
poweredge r570 firmware
≤ 1.2.6
dell
poweredge r470 firmware
≤ 1.2.6
dell
poweredge r6715 firmware
≤ 1.1.2
dell
poweredge r7715 firmware
≤ 1.1.2
dell
poweredge r6725 firmware
≤ 1.1.3
dell
poweredge r7725 firmware
≤ 1.1.3
dell
poweredge r660 firmware
≤ 2.5.4
dell
poweredge r760 firmware
≤ 2.5.4
+102 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V13.3.3
  • V17.2.1
  • V11.2.1

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces access restrictions on the iDRAC remote interface so that even high-privileged accounts cannot retrieve sensitive BIOS/firmware data beyond their authorized scope.

prevent

Requires explicit authorization, encryption, and usage restrictions for all remote management connections to iDRAC, blocking the attack vector described in the CVE.

prevent

Limits the set of privileges granted to remote administrators, reducing the amount of sensitive information that can be disclosed if the vulnerability is triggered.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-09 partial match
prevents

Pre-acquisition hardware integrity assessment can identify devices with uncleared debug exposure before purchase.

PR.PS-03 partial match
prevents

Hardware replacement policy can retire devices whose debug interfaces fail to clear sensitive state.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing in development can detect uncleared debug information before release.

degrades

Cryptographic key management and secure handling requirements reduce exposure of sensitive values during debug entry.

prevents

Secure system architecture and engineering principles directly address clearing of sensitive data on debug transitions.

degrades

Secure coding practices can mandate explicit clearing of debug registers and memory.

degrades

Test information protection includes ensuring debug artifacts do not leak sensitive data.

References