dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-10544

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 2026.1.21.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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 neutralization of special elements in the built-in PAM provider password rotation templates in Devolutions Server allows an authenticated user with write access to a vault to execute arbitrary commands on the systems managed by the affected PAM provider. This issue affects : * Devolutions Server 2026.2.4.0 * Devolutions Server 2026.1.20.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 confidence

Improper neutralization of special elements in Devolutions Server's built-in PAM provider password rotation templates allows command injection. An authenticated user with vault write access can execute arbitrary commands on systems managed by the affected PAM provider through maliciously crafted password rotation templates.

MitigationApply vendor-supplied patch for Devolutions Server. Restrict vault write access to trusted administrators only until patch is applied.

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.21.0= 2026.2.4.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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Identify Devolutions Server version
    Locate the installed Devolutions Server instance and retrieve its version number through the administration console, about page, or installed software inventory
    Affected if The installed version is lower than 2026.1.21.0 or exactly equals 2026.2.4.0
  2. Confirm PAM provider is in use
    Check if the built-in PAM provider module is enabled or configured in the Devolutions Server administration interface under PAM or privileged access management settings
    Affected if PAM provider is enabled and password rotation templates are configured
  3. Review password rotation template configurations
    Examine the password rotation templates within the PAM provider settings for any custom scripts or command execution definitions
    Affected if Custom password rotation templates exist that execute system commands or scripts during credential rotation
  4. Audit vault write access permissions
    Review user and group permissions on vaults to identify accounts with write access to the PAM-managed vault entries
    Affected if Any user account has write access to vaults containing PAM provider credentials
  5. Inspect for recent authentication and command execution logs
    Review Devolutions Server logs for suspicious command execution events originating from PAM password rotation operations
    Affected if Unexpected or unauthorized command executions appear in logs associated with password rotation activities

You are affected if running Devolutions Server version 2026.1.x below 2026.1.21.0 or exactly 2026.2.4.0, with the PAM provider password rotation feature enabled and configured.

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.21.0 or later
Fixed in 2026.1.21.0
Interim mitigation

Apply vendor-supplied patch for Devolutions Server. Restrict vault write access to trusted administrators only until patch is applied.

Recommended fix High confidence

Devolutions Server 2026.1.21.0 or later (2026.2.5.0+)

  1. Identify your current Devolutions Server version by checking the About section in the application or using the Administration module
  2. Download Devolutions Server version 2026.1.21.0 or later from the official Devolutions download portal
  3. Review the upgrade documentation and release notes for any specific upgrade requirements
  4. Perform a backup of your Devolutions Server database and configuration before upgrading
  5. Execute the upgrade installer on the Devolutions Server instance
  6. Verify the upgrade was successful by checking the version number in the Administration module
  7. Test PAM provider functionality, particularly password rotation templates, to confirm the vulnerability is remediated
  8. Review audit logs to ensure no unauthorized command execution occurred prior to the upgrade
Caveat Review release notes for any configuration or feature changes between your current version and the upgrade target; test in non-production environment first

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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