CVE-2025-5334
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 · uneditedExposure of private personal information to an unauthorized actor in the user vaults component of Devolutions Remote Desktop Manager allows an authenticated user to gain unauthorized access to private personal information. Under specific circumstances, entries may be unintentionally moved from user vaults to shared vaults when edited by their owners, making them accessible to other users. This issue affects the following versions : * Remote Desktop Manager Windows 2025.1.34.0 and earlier * Remote Desktop Manager macOS 2025.1.16.3 and earlier * Remote Desktop Manager Android 2025.1.3.3 and earlier * Remote Desktop Manager iOS 2025.1.6.0 and earlier
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 confidenceThis is an information disclosure vulnerability in Devolutions Remote Desktop Manager where authenticated users' private vault entries can be unintentionally moved to shared vaults during edit operations. When the entry owner edits their private entry, it may inadvertently become accessible to other users in the shared vault, exposing private personal information.
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<= 2025.1.16.3< 2025.1.37.0< 2025.2.0.0< 2025.2.0.17CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed version of Remote Desktop ManagerOpen the application and navigate to Help > About, or check the application's version through your system's installed programs list. Compare the version number to the affected ranges: versions <= 2025.1.16.3, < 2025.1.37.0, < 2025.2.0.0, or < 2025.2.0.17.Affected if The installed version falls within any of the affected version ranges.
-
Identify shared vaults in your environmentIn Remote Desktop Manager, open the vault management panel and list all vaults configured as shared vaults. Note the names and locations of these shared vaults.Affected if Shared vaults exist and users have private vaults alongside them.
-
Review shared vault entries for unexpected contentOpen each shared vault and examine the entries for any that contain personal, credentials, or data that should logically belong to individual users rather than being shared. Cross-reference with users who have private vaults.Affected if Entries exist in shared vaults that contain personally identifiable information, personal credentials, or data that appears to belong to a specific individual rather than being intended for team sharing.
-
Audit vault entry ownership and historyIf available, use the vault audit log or entry history feature to identify entries that were moved between vaults or had their permissions changed, particularly around the time users performed edit operations.Affected if Entries show vault transfer or permission changes that were not intentionally performed by the owner.
You are affected if your installed version is within the affected ranges AND you have users with private vaults who have edited entries that may have been unintentionally moved to shared vaults.
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 · scoped2025.1.37.02025.2.0.02025.2.0.17
Update affected Remote Desktop Manager installations to versions newer than 2025.1.34.0 (Windows), 2025.1.16.3 (macOS), 2025.1.3.3 (Android), and 2025.1.6.0 (iOS). Additionally, audit shared vault entries to identify any that may have been unintentionally moved from user vaults.
Upgrade to the latest available version of Remote Desktop Manager for your platform (Windows > 2025.1.34.0, macOS > 2025.1.16.3, Android > 2025.1.3.3, iOS > 2025.1.6.0)
- 1. Identify the platform(s) in use (Windows, macOS, Android, or iOS) from the affected Remote Desktop Manager installations
- 2. For Windows users: upgrade to a version newer than 2025.1.34.0 (e.g., 2025.1.37.0 or later)
- 3. For macOS users: upgrade to a version newer than 2025.1.16.3
- 4. For Android users: upgrade to a version newer than 2025.1.3.3
- 5. For iOS users: upgrade to a version newer than 2025.1.6.0
- 6. Download the latest version from the official Devolutions website or your licensed version's update channel
- 7. After upgrading, review vault entries to confirm no unintended data exposure has occurred
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5334 — 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-5334 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