CVE-2025-46364
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 CloudLink, versions prior to 8.1.1, contain a vulnerability where a privileged user with known password can run CLI Escape Vulnerability to gain control of system.
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 confidenceDell CloudLink versions before 8.1.1 contain a CLI escape vulnerability that allows a privileged user with an existing password to escape the intended CLI sandbox and gain full control of the underlying system. This is a privilege escalation/escape issue rather than an initial access vulnerability.
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< 8.1.1CVSS 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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Determine Dell CloudLink versionLocate the installed version of Dell CloudLink in the system information, web UI, or CLI (using commands like 'show version' or similar). Compare this version number against the affected range of versions before 8.1.1.Affected if The installed version is any version prior to 8.1.1 (e.g., 8.1.0, 8.0.x, 7.x, etc.)
-
Confirm CLI access is availableVerify that the CLI interface is enabled and accessible on the Dell CloudLink system. Check system configuration or documentation for how CLI is provisioned.Affected if CLI access is enabled and a privileged user account exists with a valid password for CLI authentication
-
Identify privileged CLI usersReview the list of users configured for CLI access with elevated or administrative privileges. These are the accounts that could potentially exploit this escape vulnerability.Affected if One or more privileged users with CLI access and an existing password are configured in the system
A user is affected if Dell CloudLink is running any version prior to 8.1.1 AND has CLI access enabled with at least one privileged user account that has an existing password.
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 · scoped8.1.1
Upgrade Dell CloudLink to version 8.1.1 or later to obtain the vendor patch. As an immediate compensating control, ensure privileged CLI credentials are tightly controlled and monitor for unusual command execution.
8.1.1
- 1. Back up the current Dell CloudLink configuration and data according to Dell documentation
- 2. Download Dell CloudLink version 8.1.1 or later from Dell support portal (www.dell.com)
- 3. Review Dell upgrade documentation for CloudLink 8.1.1 to ensure prerequisites are met
- 4. Apply the upgrade following the documented upgrade procedure for CloudLink
- 5. After upgrade completes, verify the system is running version 8.1.1 or later
- 6. Confirm the CLI Escape vulnerability is resolved by testing that privileged users cannot escape to system control
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46364 — 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-46364 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