dbcve.org
Idrac10 FirmwareOperating system · Dell

CVE-2026-35155

HIGH · 7.1 CVSS v3.1 Published 2026-04-29
Fix available
A fix is available. Upgrade to 1.30.10.50 or later.
See remediation →
75/100
Remediation priority · High
Remotely reachable

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 · unedited
Dell iDRAC10, versions 1.20.70.50 and 1.30.05.10, contains an Insufficiently Protected Credentials vulnerability. A race condition vulnerability exists that could allow an authenticated low‑privileged attacker to gain elevated access.

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 · moderate confidence

Dell iDRAC10 versions 1.20.70.50 and 1.30.05.10 contain a race condition vulnerability in credential handling that allows an authenticated low-privileged user to escalate privileges to higher access levels. The CVSS 7.1 score indicates significant exploitability with low attack complexity.

MitigationApply Dell's patched iDRAC firmware version to address the race condition in credential protection. Restrict low-privileged user access until the patch is applied.

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
Idrac10 FirmwareOperating system
Affected:< 1.30.10.50

CVSS 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
Network
Complexity
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check iDRAC firmware version
    Access iDRAC web interface or use racadm command: racadm get iDRAC.WebServer.1.Static# or check via iDRAC Settings > Firmware > Current Version
    Affected if Version is below 1.30.10.50 (specifically 1.20.70.50 or 1.30.05.10)
  2. Confirm iDRAC10 model
    Verify the vulnerable model is iDRAC10 by checking hardware info via iDRAC web interface or racadm get iDRAC.Info
    Affected if Device is iDRAC10 (iDRAC9 and later models are not affected)
  3. Identify low-privilege user accounts
    List all iDRAC users with their privilege levels using: racadm get iDRAC.Users.*.UserName and racadm get iDRAC.Users.*.Privilege
    Affected if Any low-privilege user accounts (less than Administrator) exist on the system
  4. Verify user authentication is enabled
    Check iDRAC user authentication settings: racadm get iDRAC.WebServer.1.SSLEncryption
    Affected if Remote authentication and web interface are enabled, allowing authenticated users to access the vulnerable credential handling code

User is affected if iDRAC10 firmware version is below 1.30.10.50 and low-privileged user accounts exist that could exploit the race condition for privilege escalation

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.30.10.50 or later
Fixed in 1.30.10.50
Interim mitigation

Apply Dell's patched iDRAC firmware version to address the race condition in credential protection. Restrict low-privileged user access until the patch is applied.

Recommended fix High confidence

iDRAC10 Firmware version 1.30.10.50 or later

  1. 1. Back up the current iDRAC configuration using the iDRAC web interface or racadm utility
  2. 2. Download the iDRAC10 firmware version 1.30.10.50 or later from Dell's support website
  3. 3. Upload the firmware update through the iDRAC web interface under 'Maintenance' > 'System Update' > 'Firmware Update', or use racadm command: racadm update -f <firmware_file>
  4. 4. Wait for the firmware update to complete and for iDRAC to reboot
  5. 5. Verify the new firmware version is installed by checking iDRAC web interface or running: racadm get iDRAC.WebServer.1.1
  6. 6. After upgrade, review user privileges and reset credentials for sensitive accounts as a security best practice
Caveat Firmware updates may briefly interrupt iDRAC connectivity; ensure out-of-band management access is stable before proceeding; review release notes for any known compatibility issues

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Idrac10 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35155 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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