dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-11957

HIGH · 8.4 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to 2025.2.14.0 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper authorization in the temporary access workflow of Devolutions Server 2025.2.12.0 and earlier allows an authenticated basic user to self-approve or approve the temporary access requests of other users and gain unauthorized access to vaults and entries 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 · high confidence

Improper authorization in the temporary access workflow of Devolutions Server allows authenticated basic users to self-approve or approve other users' temporary access requests via crafted API requests, bypassing role-based access controls and gaining unauthorized access to vaults and entries.

MitigationUpgrade Devolutions Server to a version newer than 2025.2.12.0 which contains the vendor patch for proper authorization enforcement in the temporary access workflow.

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
Devolutions ServerApplication
Affected:< 2025.2.14.0

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Devolutions Server version
    Locate the Devolutions Server installation and check the installed version number. This is typically found in the application itself, installation files, or system information about the installed software.
    Affected if The installed version is lower than 2025.2.14.0 (for example, 2025.2.12.0 or earlier)
  2. Confirm temporary access workflow is enabled
    Check the Devolutions Server configuration or settings to determine if the temporary access feature is active. This may be visible in the administrative interface or configuration files.
    Affected if The temporary access feature is enabled and available for use in the environment
  3. Review audit logs for approval actions
    Examine the Devolutions Server security or audit logs for events related to temporary access approvals. Look for records of approval actions performed on temporary access requests.
    Affected if Basic or standard users are shown as having approved temporary access requests (which should require elevated privileges)
  4. Inspect for unauthorized vault or entry access
    Review access logs or vault entry access records to identify if basic users accessed vaults or entries through temporary access requests they should not have been able to approve.
    Affected if Basic users accessed sensitive vaults or entries via temporary access that was approved without proper authorization enforcement

You are affected if Devolutions Server version is below 2025.2.14.0 and the temporary access workflow is in use, with evidence of basic users approving access requests they should not have permissions to approve.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.2.14.0 or later
Fixed in 2025.2.14.0
Interim mitigation

Upgrade Devolutions Server to a version newer than 2025.2.12.0 which contains the vendor patch for proper authorization enforcement in the temporary access workflow.

Recommended fix High confidence

Devolutions Server 2025.2.14.0

  1. 1. Back up your current Devolutions Server database and configuration.
  2. 2. Download Devolutions Server version 2025.2.14.0 or later from the official Devolutions website (devolutions.net).
  3. 3. Stop the Devolutions Server service before performing the upgrade.
  4. 4. Run the installer/upgrade package for version 2025.2.14.0.
  5. 5. Follow the on-screen upgrade instructions, ensuring database migration completes successfully.
  6. 6. Restart the Devolutions Server service after the upgrade finishes.
  7. 7. Verify the temporary access workflow now properly enforces authorization checks.
  8. 8. Confirm that basic users can no longer approve their own or others' temporary access requests through the API.
Caveat Review release notes for any changes to temporary access functionality or API behavior before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11957 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11957 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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