CVE-2025-26482
Dell Idrac9 Firmware ≤ 7.00.00.181
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:NSummary
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
- 🇪🇺 ENISA EUVD: EUVD-2025-31169
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
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
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.
Requires explicit authorization, encryption, and usage restrictions for all remote management connections to iDRAC, blocking the attack vector described in the CVE.
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.
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.
Security testing in development can detect uncleared debug information before release.
Cryptographic key management and secure handling requirements reduce exposure of sensitive values during debug entry.
Secure system architecture and engineering principles directly address clearing of sensitive data on debug transitions.
Secure coding practices can mandate explicit clearing of debug registers and memory.
Test information protection includes ensuring debug artifacts do not leak sensitive data.