How to Fix CVE-2026-3519: Command injection in ECS Connections Manager

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

What is CVE-2026-3519?

OS Command Injection Remote Code Execution Vulnerability in API in Progress ADC Products allows an authenticated attacker with “VS Administration” permissions to execute arbitrary commands on the LoadMaster appliance by exploiting unsanitized input in the 'aclcontrol' command

Am I affected?

Run the version check that matches your platform:

# Linux
dpkg -s ecs 2>/dev/null | grep -i version
rpm -q ecs 2>/dev/null
ecs --version 2>/dev/null

Compare what you see against the Affected row above (Progress Software LoadMaster V7.2.45.0 to <V7.2.63.0; Progress Software ECS Connections Manager V7.2.49.0 to <V7.2.63.0; Progress Software Object Scale Connection Manager V7.2.62.0 to <V7.2.63.0; Progress Software MOVEit WAF V7.2.62.0 to <V7.2.63.0). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-3519

The primary fix is to upgrade ECS Connections Manager to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: LoadMaster V7.2.63.0; ECS Connections Manager V7.2.63.0; Object Scale Connection Manager V7.2.63.0; MOVEit WAF V7.2.63.0.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade ecs
ecs --version 2>/dev/null || dpkg -s ecs | grep -i version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --security ecs -y
rpm -q ecs

SUSE / openSUSE

sudo zypper patch --category security
rpm -q ecs

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-3519 affecting ECS Connections Manager
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-3519-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] Detecting installed version of ECS Connections Manager"
    $pkg = winget list --id "ECS_Connections_Manager" 2>$null
    Write-Host $pkg

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

    Write-Host "[3/4] Applying upgrade to LoadMaster V7.2.63.0; ECS Connections Manager V7.2.63.0; Object Scale Connect..."
    winget upgrade --id "ECS_Connections_Manager" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "ECS_Connections_Manager"
    Write-Host "Fix 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-3519 affecting ECS Connections Manager
# Detect -> backup -> upgrade -> verify -> log.

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

echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
    dpkg -s ecs 2>/dev/null | grep -i version || echo "ecs not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q ecs || echo "ecs not installed via rpm"
fi

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

echo "[3/4] Applying upgrade (target: LoadMaster V7.2.63.0; ECS Connections Manager V7.2.63.0; Object Scale Connect...)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y ecs
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y ecs
elif command -v yum >/dev/null; then
    yum update -y ecs
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
    dpkg -s ecs 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q ecs
fi
echo "Done. Restart any running daemons that loaded the old library."

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network restriction (Linux, nftables)

# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Service-level fallback

# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop ecs
sudo systemctl disable ecs

How to verify the fix worked

# Linux
ecs --version 2>/dev/null || dpkg -s ecs | grep -i version
rpm -q ecs 2>/dev/null || true

# Windows
winget list | findstr /I "ecs"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above LoadMaster V7.2.63.0; ECS Connections Manager V7.2.63.0; Object Scale Connection Manager V7.2.63.0; MOVEit WAF V7.2.63.0. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Related fixes

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

• How to Fix CVE-2026-36388: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripti — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripti
• How to Fix CVE-2026-44088: Unrestricted File Upload in SzafirHost — Unrestricted File Upload in SzafirHost
• How to Fix CVE-2026-24762: Critical Vulnerability in rustfs , Critical Vulnerability in rustfs
• How to Fix CVE-2026-3737: Improper Authorization in Pet Grooming Management Software , Improper Authorization in Pet Grooming Management Software
• How to Fix CVE-2026-44560: Missing Authorization in open-webui , Missing Authorization in open-webui

Is CVE-2026-3519 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

8.4 (high). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

• Official vendor advisory: https://community.progress.com/s/article/LoadMaster-Security-Vulnerabilites-CVE-2026-3517-CVE-2026-3518-CVE-2026-3519-CVE-2026-4048-CVE-2026-21876
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3519

*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.*