Barracuda Networks RMM vulnerabilities

5 vulnerabilities

Known vulnerabilities in Barracuda Networks RMM, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

10CVE-2025-34394barracuda networksrmm+1
EPSS score
0.71%
Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, exposes a .NET Remoting service that is insufficiently protected against deserialization of arbitrary types. This can lead to remote code execution.10CVE-2025-34392barracuda networksrmm+1
EPSS score
24.72%
Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not verify the URL defined in an attacker-controlled WSDL that is later loaded by the application. This can lead to arbitrary file write and remote code execution via webshell upload.10CVE-2025-34393barracuda networksrmm+1
EPSS score
0.71%
Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not correctly verify the name of an attacker-controlled WSDL service, leading to insecure reflection. This can result in remote code execution through either invocation of arbitrary methods or deserialization of untrusted types.8.7CVE-2025-34395barracuda networksrmm+1
EPSS score
0.75%
Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, exposes a .NET Remoting service in which an unauthenticated attacker can invoke a method vulnerable to path traversal to read arbitrary files. This vulnerability can be escalated to remote code execution by retrieving the .NET machine keys.8.5CVE-2026-22676barracuda networksrmm
EPSS score
0.10%
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.