● Critical · CVSS 9.8

How to Fix CVE-2026-2590: Improper certificate validation in Remote Desktop Manager

Q: What is the CVSS score for CVE-2026-2590?

9.8 (Critical). Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`.

Q: Where is the official advisory for CVE-2026-2590?

The vendor advisory is at [https://devolutions.net/security/advisories/DEVO-2026-0005](https://devolutions.net/security/advisories/DEVO-2026-0005). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2590.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-2590 is a improper certificate validation in Devolutions Remote Desktop Manager. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	9.8 (Critical)
Actively exploited?	No public listing in CISA KEV
Affected	Remote Desktop Manager 0 to <=2025.3.30
Fixed in	See vendor advisory
Type (CWE)	CWE-295 Improper Certificate Validation

What is CVE-2026-2590?

Improper

enforcement of the Disable password saving in vaults setting in the

connection entry component in Devolutions Remote Desktop Manager 2025.3.30 and earlier allows an authenticated user to persist credentials in vault entries,

potentially exposing sensitive information to other users, by creating

or editing certain connection types while password saving is disabled. The CVSS base score is 9.8 (Critical), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://devolutions.net/security/advisories/DEVO-2026-0005.

Am I affected?

Check the version of Remote Desktop Manager you are running and compare it against the Affected row above (Remote Desktop Manager 0 to <=2025.3.30). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s remote-desktop-manager 2>/dev/null | grep -i ^Version
rpm -q remote-desktop-manager 2>/dev/null
command -v remote-desktop-manager >/dev/null && remote-desktop-manager --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Remote Desktop Manager*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Remote Desktop Manager" 2>$null

How to fix CVE-2026-2590

Upgrade Remote Desktop Manager to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade remote-desktop-manager
dpkg -s remote-desktop-manager | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh remote-desktop-manager -y
# or for older releases:
sudo yum update remote-desktop-manager -y
rpm -q remote-desktop-manager

SUSE / openSUSE


sudo zypper refresh
sudo zypper update remote-desktop-manager
rpm -q remote-desktop-manager

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-2590 affecting Remote Desktop Manager
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-2590-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Remote Desktop Manager*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\remote-desktop-manager-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Remote Desktop Manager" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Remote Desktop Manager" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Remote Desktop Manager"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-2590 affecting Remote Desktop Manager
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-2590-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s remote-desktop-manager 2>/dev/null | grep -i ^Version || echo "remote-desktop-manager not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q remote-desktop-manager || echo "remote-desktop-manager not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-2590-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/remote-desktop-manager /etc/remote-desktop-manager.d /etc/remote-desktop-manager.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y remote-desktop-manager
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y remote-desktop-manager
elif command -v yum >/dev/null; then
    yum update -y remote-desktop-manager
elif command -v zypper >/dev/null; then
    zypper --non-interactive update remote-desktop-manager
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s remote-desktop-manager 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q remote-desktop-manager
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-2590" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-2590"

Disable the affected service (Linux)


sudo systemctl stop remote-desktop-manager 2>/dev/null || true
sudo systemctl disable remote-desktop-manager 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s remote-desktop-manager 2>/dev/null | grep -i ^Version
rpm -q remote-desktop-manager 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Remote Desktop Manager*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-40942: Cwe-670: always-incorrect control flow implementation in dsf — Cwe-670: always-incorrect control flow implementation in dsf
How to Fix CVE-2026-24157: Deserialization RCE in NeMo Framework — Deserialization RCE in NeMo Framework
How to Fix CVE-2026-36235: SQL injection in SQL , SQL injection in SQL
How to Fix CVE-2026-32252: Improper authorization in chartbrew , Improper authorization in chartbrew
How to Fix CVE-2026-22023: Path Traversal in CryptoLib , Path Traversal in CryptoLib

Is CVE-2026-2590 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-2590?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-2590?

9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Where is the official advisory for CVE-2026-2590?

The vendor advisory is at https://devolutions.net/security/advisories/DEVO-2026-0005. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2590.

References

Official vendor advisory: https://devolutions.net/security/advisories/DEVO-2026-0005
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2590
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*