Remote Desktop ManagerApplication · Devolutions

CVE-2026-12161

HIGH · 8.8 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 2026.2.8.0 or later.
See remediation →
94/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 input validation in the SSH Elevate Shell feature allows an authenticated user with permission to create or modify a shared SSH entry to execute arbitrary commands on a remote SSH host using stored elevation credentials via a crafted alternate username and user interaction with the Elevate Shell action. This affects  :  - Remote Desktop Manager 2026.2.5.0 through 2026.2.7.0 - Remote Desktop Manager 2026.1.23.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 input validation in Remote Desktop Manager's SSH Elevate Shell feature allows authenticated users with permissions to create or modify shared SSH entries to inject arbitrary commands via a crafted alternate username, exploiting stored elevation credentials.

MitigationUpgrade to a patched version (2026.2.8.0 or later for the 2026.2 branch, or vendor-released patch for 2026.1 branch). Until patched, restrict SSH entry modification permissions to only trusted administrators.

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
Remote Desktop ManagerApplication
Affected:< 2026.2.8.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

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

  1. Check installed version of Remote Desktop Manager
    Open the application, go to Help > About or check the application executable version property. Compare against the affected range: versions prior to 2026.2.8.0 are vulnerable.
    Affected if Installed version is before 2026.2.8.0
  2. Verify permission to create or modify SSH entries
    In the application, check your user profile or group permissions for the ability to create or edit shared SSH entries. This is typically found in Administration > Security or user/group permission settings.
    Affected if User account has permission to create or modify shared SSH entries
  3. Identify SSH entries with Elevate Shell configured
    Browse your remote connections database and look for SSH entries. For each SSH entry, open the properties and check if the Elevate Shell feature is enabled. This is usually found under the SSH or Security tab in entry properties.
    Affected if Any SSH entries have the Elevate Shell feature enabled with stored elevation credentials
  4. Inspect alternate username field in SSH entries
    In each SSH entry with Elevate Shell enabled, examine the Alternate username field. Look for suspicious patterns such as command separators (semicolons, pipes, ampersands), shell metacharacters, or unexpected whitespace that could indicate injection attempts.
    Affected if Any SSH entry contains an alternate username with command injection sequences or unexpected special characters

You are affected if you run a version of Remote Desktop Manager prior to 2026.2.8.0 AND have SSH entries with Elevate Shell enabled AND your account has permission to modify those entries.

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.2.8.0 or later
Fixed in 2026.2.8.0
Interim mitigation

Upgrade to a patched version (2026.2.8.0 or later for the 2026.2 branch, or vendor-released patch for 2026.1 branch). Until patched, restrict SSH entry modification permissions to only trusted administrators.

Recommended fix High confidence

Remote Desktop Manager 2026.2.8.0

  1. Download Remote Desktop Manager version 2026.2.8.0 or later from the official Devolutions website
  2. Install the update following the standard installation process
  3. Verify the installed version is 2026.2.8.0 or higher

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

Fix this in Remote Desktop Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12161 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