CVE-2026-3638
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 · uneditedImproper access control in user and role restore API endpoints in Devolutions Server 2025.3.11.0 and earlier allows a low-privileged authenticated user to restore deleted users and roles via crafted API requests.
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 confidenceDevolutions Server contains improper access control in user and role restore API endpoints where a low-privileged authenticated user can restore previously deleted users and roles through crafted API requests. This allows privilege escalation by potentially regaining access to administrative accounts or restoring roles 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< 2025.3.12.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N
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 Devolutions Server versionLocate and inspect the installed Devolutions Server version. This is typically available in the application itself (via About or Version information), in the installation directory metadata, or through the administrative web interface. Compare the version number to the affected range: versions prior to 2025.3.12.0 are vulnerable.Affected if Installed version is lower than 2025.3.12.0
-
Identify accessible API restore endpointsExamine the Devolutions Server API documentation or configuration to identify the user and role restore endpoints. These are typically REST API paths used to restore previously deleted users or roles.Affected if Restore API endpoints exist and are accessible without elevated privileges
-
Review audit logs for restore operationsInspect Devolutions Server audit logs for any restore operations performed on users or roles. Look specifically for restore actions executed by accounts that do not have administrative or elevated permissions.Affected if Audit logs show restore operations performed by low-privileged or non-administrative accounts
-
Check for deleted users and rolesReview the list of deleted (soft-deleted) users and roles within Devolutions Server. Determine whether any deleted administrative accounts or elevated-privilege roles exist that could be restored by a low-privileged user.Affected if Deleted administrative users or elevated-privilege roles exist that could be restored
A defender is affected if their Devolutions Server version is below 2025.3.12.0 AND the restore API endpoints are accessible to low-privileged authenticated users, or if evidence exists of unauthorized restore operations in logs.
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.3.12.0
Update to Devolutions Server version 2025.3.12.0 or later which contains the patch for proper authorization enforcement on restore endpoints. Additionally, review audit logs for any unauthorized restore operations performed by low-privileged accounts.
2025.3.12.0 or later
- Upgrade Devolutions Server to version 2025.3.12.0 or later to address the missing authorization vulnerability
- Verify the upgrade was successful by checking the server version in the administration console
- Test that the user and role restore API endpoints now properly enforce authorization checks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3638 — 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-2026-3638 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