dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-15637

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 2026.1.23.0 / 2026.2.12.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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 PAM SSH key and certificate retrieval endpoints in Devolutions Server 2026.2.11, 2026.1.22 allows an authenticated low-privileged user to disclose the private key of an SSH key or certificate PAM credential via a direct object reference to the credential identifier.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in Devolutions Server's PAM SSH key and certificate retrieval endpoints. An authenticated low-privileged user can access private keys of SSH credentials they don't own by directly referencing the credential identifier, bypassing intended access controls.

MitigationImplement proper authorization checks at the credential retrieval endpoints to verify the requesting user has permission to access the specific credential. Enforce principle of least privilege on credential access.

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:< 2026.1.23.0>= 2026.2.0.0, < 2026.2.12.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Determine Devolutions Server installed version
    Access the server administration interface or run the command 'dws Server version' or check the About section in the Devolutions Server management console to retrieve the exact version number
    Affected if The installed version is 2026.1.1 through 2026.1.22.x, or 2026.2.4.0 through 2026.2.11.x (any version >= 2026.1.1 and < 2026.1.23.0, or >= 2026.2.4.0 and < 2026.2.12.0)
  2. Verify PAM module is active
    In Devolutions Server administration, navigate to Modules or Plugins section and confirm the Privileged Access Management (PAM) module is enabled and configured
    Affected if PAM module is installed and active with SSH credential management capabilities
  3. Identify SSH credential entries
    Navigate to the PAM credential vault or SSH credentials management interface and list all stored SSH credentials to confirm credentials exist in the system
    Affected if There are SSH key or certificate-based credentials stored in the PAM vault
  4. Review user role assignments
    In the User Management or Access Control section, examine which users are assigned the low-privileged role (such as standard user or custom non-admin role) and have access to the PAM module
    Affected if There are authenticated users with limited (non-administrator) roles who have PAM module access
  5. Audit credential access logging
    Review Devolutions Server audit logs or access logs for the PAM SSH key/certificate retrieval endpoints, specifically look for requests where the requesting user ID differs from the credential owner
    Affected if Logs show credential retrieval events where a user accessed a credential ID that does not belong to their assigned scope

You are affected if your Devolutions Server version falls within the affected ranges AND the PAM module with SSH credentials is enabled and accessible to low-privileged users.

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 2026.1.23.0 / 2026.2.12.0 or later
Fixed in 2026.1.23.02026.2.12.0
Interim mitigation

Implement proper authorization checks at the credential retrieval endpoints to verify the requesting user has permission to access the specific credential. Enforce principle of least privilege on credential access.

Recommended fix High confidence

Upgrade to Devolutions Server 2026.1.23.0 (for 2026.1.x line) or 2026.2.12.0 (for 2026.2.x line)

  1. 1. Identify the current Devolutions Server version by checking the About or version information in the admin console.
  2. 2. Determine which release line (2026.1.x or 2026.2.x) is currently installed.
  3. 3. If running 2026.1.x (2026.1.1 through 2026.1.22), plan upgrade to version 2026.1.23.0 or later.
  4. 4. If running 2026.2.x (2026.2.4 through 2026.2.11), plan upgrade to version 2026.2.12.0 or later.
  5. 5. Create a complete backup of the Devolutions Server database and configuration files before upgrading.
  6. 6. Download the appropriate fixed version from the official Devolutions downloads page (devolutions.net).
  7. 7. Execute the upgrade following the vendor's standard upgrade procedure for Devolutions Server.
  8. 8. After upgrade, verify the fix by attempting to confirm that low-privileged users can no longer access SSH private keys or certificates belonging to other users via direct object references.
Caveat Review release notes for any configuration or feature changes between versions; standard upgrade risks apply (test in non-production first)

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15637 — 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-2026-15637 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