dbcve.org
Link Following (Symlink)Weakness · CWE-59

CVE-2026-28262

MEDIUM · 6.0 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated

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 iDRAC Tools, versions prior to 11.4.1.0, contains an Improper Link Resolution Before File Access ('Link Following') vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Information tampering.

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 iDRAC Tools versions prior to 11.4.1.0 contain a link following (symlink) vulnerability where the software improperly resolves file paths before accessing files. A low-privileged local attacker could exploit this by placing malicious symbolic links in certain directories, potentially allowing tampering of information files that the affected tool accesses.

MitigationUpgrade Dell iDRAC Tools to version 11.4.1.0 or later. If immediate upgrading is not feasible, restrict local access to the system and monitor for unauthorized symbolic link creation in iDRAC tool directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/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. Identify installed Dell iDRAC Tools version
    On Windows, check Add/Remove Programs or examine the installed package details via 'Get-WmiObject -Class Win32_Product' filtering for 'iDRAC' or 'Dell iDRAC'. On Linux, check the RPM/DEB package: 'rpm -qa | grep -i idrac' or 'dpkg -l | grep -i idrac'. Check the version from the output.
    Affected if The displayed version is lower than 11.4.1.0 (for example, 11.3.0.0, 10.x.x.x, etc.) or no version is returned.
  2. Confirm the iDRAC Tools installation path
    Locate the primary installation directory. On Windows, typical paths include 'C:\Program Files\Dell\iDRAC Tools' or 'C:\Program Files (x86)\Dell\iDRAC Tools'. On Linux, check '/opt/dell/idrac-tools' or '/usr/local/bin' for iDRAC binaries.
    Affected if The software is installed in a directory accessible to untrusted local users.
  3. Verify file permissions on iDRAC Tools directories
    On Windows, right-click the iDRAC Tools folder, select Properties, then Security tab. Check if 'Users' or 'Authenticated Users' have Write or Modify permissions. On Linux, run 'ls -la /opt/dell/idrac-tools' or the identified path to view permissions.
    Affected if Non-admin users have Write or Modify permissions on iDRAC Tools directories or files.
  4. Inspect for writable symbolic links
    Search for symbolic links within iDRAC Tools directories: 'dir /AL /S C:\Program Files\Dell\iDRAC Tools' on Windows, or 'find /opt/dell/idrac-tools -type l -ls' on Linux. Check if any point to locations outside the tool's directory.
    Affected if Writable symbolic links exist that could be manipulated by low-privileged users.

A system is affected if Dell iDRAC Tools version is prior to 11.4.1.0 AND untrusted local users have write access to directories or symbolic links used by the iDRAC Tools software.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Dell iDRAC Tools to version 11.4.1.0 or later. If immediate upgrading is not feasible, restrict local access to the system and monitor for unauthorized symbolic link creation in iDRAC tool directories.

Recommended fix Moderate confidence

Dell iDRAC Tools version 11.4.1.0

  1. 1. Identify the current version of Dell iDRAC Tools installed on the system
  2. 2. Navigate to the Dell Support website (www.dell.com) and locate the Dell iDRAC Tools download page
  3. 3. Download Dell iDRAC Tools version 11.4.1.0 or later
  4. 4. Follow Dell's standard installation or upgrade procedures for iDRAC Tools
  5. 5. Verify the installation completed successfully and the version is now 11.4.1.0 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28262 — 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-28262 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