CVE-2025-36611
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 and Dell Security Management Server, versions prior to 11.11.0, contain an Improper Link Resolution Before File Access ('Link Following') 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 and Dell Security Management Server versions prior to 11.11.0 contain a symlink following vulnerability (CWE-59) where improper link resolution before file access allows a local authenticated user to potentially escalate privileges by manipulating file system links to access sensitive resources or execute code with elevated permissions.
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.11.0.1< 11.11.0.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.
-
Identify installed Dell productCheck if Dell Encryption or Dell Security Management Server is installed on the system by reviewing installed applications or servicesAffected if Either Dell Encryption or Dell Security Management Server is present on the system
-
Determine Dell Encryption versionLocate the installed version of Dell Encryption through the application itself, installation directory, or system registry if applicableAffected if The installed version is lower than 11.11.0.1
-
Determine Dell Security Management Server versionLocate the installed version of Dell Security Management Server through the application itself, installation directory, or system registry if applicableAffected if The installed version is lower than 11.11.0.2
The system is affected if Dell Encryption version is below 11.11.0.1 or Dell Security Management Server version is below 11.11.0.2, as these versions contain the symlink following vulnerability that allows local privilege escalation.
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.11.0.111.11.0.2
Upgrade Dell Encryption and Dell Security Management Server to version 11.11.0 or later to remediate this vulnerability. Apply the update following Dell's standard upgrade procedures with appropriate change management controls.
Dell Encryption: 11.11.0.1 or later; Dell Security Management Server: 11.11.0.2 or later
- Identify the specific product in use (Dell Encryption or Dell Security Management Server)
- Locate the current installed version in the system
- For Dell Encryption: upgrade to version 11.11.0.1 or later
- For Dell Security Management Server: upgrade to version 11.11.0.2 or later
- After upgrade, verify the new version is correctly installed
- Test that the application functions normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36611 — 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-36611 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