⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.5

How to Fix CVE-2026-22676: Incorrect permission assignment in RMM

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

⚡ At a glance
Severity8.5 (High)
Actively exploited?No public listing in CISA KEV
AffectedBarracuda Networks RMM 0 to <2025.2.2
Fixed inRMM 2025.2.2
Type (CWE)CWE-732: Incorrect Permission Assignment for Critical Resource

What is CVE-2026-22676?

Barracuda RMM versions prior to 2025.2.2 contain a privilege escalation vulnerability that allows local attackers to gain SYSTEM-level privileges by exploiting overly permissive filesystem ACLs on the C:\Windows\Automation directory. Attackers can modify existing automation content or place attacker-controlled files in this directory, which are then executed under the NT AUTHORITY\SYSTEM account during routine automation cycles, typically succeeding within the next execution cycle.

Am I affected?

Run the version check that matches your platform:


# Windows
winget list | findstr /I "rmm"
Get-WmiObject Win32_Product | Where-Object { $_.Name -like "*RMM*" } | Select-Object Name, Version

Compare what you see against the Affected row above (Barracuda Networks RMM 0 to <2025.2.2). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-22676

The primary fix is to upgrade RMM to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: RMM 2025.2.2.

Windows (PowerShell, run as administrator)


# Check installed version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

# Apply latest Microsoft security updates (Windows Update)
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck
Import-Module PSWindowsUpdate
Get-WindowsUpdate -MicrosoftUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -AutoReboot

# Or via winget for application-level patches
winget upgrade --all --accept-source-agreements --accept-package-agreements

If the affected component is a third-party application, identify the package and run:


winget upgrade --id <vendor.product>

Replace <vendor.product> with the actual winget identifier (run winget search RMM to find it).

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-22676 affecting RMM
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-22676-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 RMM"
    $pkg = winget list --id "RMM" 2>$null
    Write-Host $pkg

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

    Write-Host "[3/4] Applying upgrade to RMM 2025.2.2"
    winget upgrade --id "RMM" --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 "RMM"
    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-22676 affecting RMM
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-22676-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 rmm 2>/dev/null | grep -i version || echo "rmm not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q rmm || echo "rmm not installed via rpm"
fi

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

echo "[3/4] Applying upgrade (target: RMM 2025.2.2)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y rmm
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y rmm
elif command -v yum >/dev/null; then
    yum update -y rmm
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 rmm 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q rmm
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.

Windows firewall isolation


# Allow only management subnet to reach the vulnerable service
New-NetFirewallRule -DisplayName "Restrict RMM" `
    -Direction Inbound -Action Block -RemoteAddress Any `
    -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Allow Mgmt RMM" `
    -Direction Inbound -Action Allow -RemoteAddress 10.0.0.0/8 `
    -Protocol TCP -LocalPort 443

Service-level fallback


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

How to verify the fix worked


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


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

Expected: the reported version is at or above RMM 2025.2.2. 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

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

Is CVE-2026-22676 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.5 (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

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