CVE-2025-36564
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 Encryption Admin Utilities versions prior to 11.10.2 contain an Improper Link Resolution vulnerability. A local malicious user could potentially exploit this vulnerability, leading to privilege escalation.
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 Encryption Admin Utilities versions prior to 11.10.2 contain an Improper Link Resolution (CWE-59) vulnerability. A local authenticated attacker could exploit this by creating malicious symbolic links that the vulnerable application follows, potentially allowing execution with elevated privileges.
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< 11.10.2CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Dell Encryption Admin Utilities is installedCheck for the presence of Dell Encryption Admin Utilities on the system. On Windows, look in Program Files for 'Dell Encryption' or 'Dell Encryption Admin Utilities'. On Linux, check for RPM/DEB packages with commands like 'rpm -qa | grep -i dell' or 'dpkg -l | grep -i dell'. Also check for service entries named 'DellEncryption' or similar.Affected if The software is installed on the system
-
Determine installed versionRetrieve the version of Dell Encryption Admin Utilities. On Windows, check Add/Remove Programs, the application's About dialog, or check version info on the executable files in the installation directory. On Linux, use package management commands like 'rpm -qi <package_name>' or check /opt/dellEncryption directory for version files.Affected if The installed version is lower than 11.10.2
-
Check if application runs with elevated privilegesExamine the service configuration or startup method for Dell Encryption Admin Utilities. On Windows, check Services.msc for the service entry and look at 'Log On As' settings. On Linux, check init/systemd service files for privilege level. Also check file ownership and permissions on the installation directory.Affected if The application runs with administrative or SYSTEM/root privileges and the version is below 11.10.2
-
Verify attacker-controlled write locations existIdentify directories where Dell Encryption Admin Utilities creates or modifies files. Check temp directories, log directories, and configuration paths the application uses. Look for world-writable directories that an authenticated local user could potentially place symbolic links into.Affected if The application writes to locations accessible to authenticated local users and version is below 11.10.2
You are affected if Dell Encryption Admin Utilities is installed with a version lower than 11.10.2 and runs with elevated privileges in an environment where local authenticated users can create symbolic links in directories the application uses.
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 · scoped11.10.2
Upgrade Dell Encryption Admin Utilities to version 11.10.2 or later to obtain the vendor patch for this vulnerability.
11.10.2
- Obtain Dell Encryption Admin Utilities version 11.10.2 or later from Dell support portal or authorized distribution channels
- Follow Dell's standard upgrade procedure for Encryption Admin Utilities, which typically involves running the installer with appropriate administrative privileges
- After upgrade, verify the installed version matches 11.10.2 or later using the product's version checking mechanism
- Test that normal administrative functions of Dell Encryption Admin Utilities continue to operate correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36564 — 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-36564 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