Skip to main content

Barracuda RMM CVE-2025-34393

CRITICAL
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') (CWE-470)
2025-12-10 disclosure@vulncheck.com
10.0
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Service Center over network
  2. Delivery
    Send crafted WSDL service name
  3. Exploit
    Bypass insecure name verification
  4. Execution
    Trigger unsafe reflection/deserialization
  5. Persist
    Execute arbitrary code on host
  6. Impact
    Pivot to managed endpoints

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V15 - Secure Coding and Architecture Reflection safety, class allowlisting
Exploitation Conditions

The specific prerequisite is that the Barracuda RMM Service Center (versions prior to 2025.1.1) processes an attacker-controlled WSDL service name without correctly verifying it, enabling insecure reflection into arbitrary method invocation or untrusted-type deserialization. Per AV:N/AC:L/PR:N/UI:N this is remote unauthenticated exploitation requiring no user interaction against the default-reachable Service Center service; the only effective limiting factors are network reachability of the Service Center endpoint (typically the central management server rather than managed agents) and running a version below 2025.1.1 - upgrading to 2025.1.1 removes the condition.

Impact

All severity signals point to maximum theoretical risk: the CVSS 4.0 base vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes remote, unauthenticated, low-complexity exploitation with high confidentiality, integrity, and availability impact on both the vulnerable system and subsequent systems (VC/VI/VA:H and SC/SI/SA:H), yielding a 10.0 score. CWE-470 (unsafe reflection) leading to arbitrary method invocation or deserialization of untrusted types is a well-understood, reliable RCE class. However, the exploitation-likelihood signals are notably softer and should temper prioritization: EPSS is only 0.71% (52nd percentile), the CVE is NOT on the CISA KEV list, and no public proof-of-concept is referenced - so this is a high-CVSS flaw without current evidence of active exploitation or public weaponization. The conflict to flag: raw severity is maximal while real-world exploitation probability is currently low/unproven. No SSVC decision data (automatable, exploitation status) was provided in the input, so an SSVC-based priority cannot be computed here. Net assessment - because Barracuda RMM is a privileged management platform whose compromise cascades to all managed endpoints, this warrants prompt patching despite low EPSS; the low EPSS likely reflects limited attacker attention to date rather than low exploitability.

Exploit ScenarioDerived

A remote, unauthenticated attacker reaches the Barracuda RMM Service Center over the network and supplies a crafted request referencing an attacker-controlled WSDL service name that the application fails to validate. The insecure reflection resolves this into invocation of arbitrary methods or deserialization of untrusted types, yielding remote code execution on the Service Center host. Per CVSS AV:N/AC:L/PR:N/UI:N, no authentication, user interaction, or special timing is required; no public exploit code is identified at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Remote code execution in Barracuda RMM's Service Center component (versions prior to 2025.1.1) allows unauthenticated network attackers to run arbitrary code on the server by supplying a malicious WSDL whose service name is not properly validated, enabling insecure reflection into arbitrary method calls or deserialization of untrusted types. The CVSS 4.0 base vector (AV:N/AC:L/AT:N/PR:N/UI:N) rates it 10.0, matching our independent CVSS 3.1 assessment of 10.0, meaning remote, unauthenticated, no-interaction exploitation with high confidentiality, integrity, and availability impact on both the vulnerable host and subsequent systems. No public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS is only 0.71% (52nd percentile), so severity is maximum but observed exploitation activity remains low; the primary practical limiter is network reachability of the Service Center endpoint, typically the central management server rather than the managed agents.

RemediationAI

Vendor-released patch: upgrade Barracuda RMM to version 2025.1.1, which removes the insecure reflection condition, per the release notes at https://download.mw-rmm.barracudamsp.com/PDF/2025.1.1/RN_BRMM_2025.1.1_EN.pdf; consult the Barracuda MSP product page (https://www.barracuda.com/products/msp/network-protection/rmm) and the VulnCheck advisory (https://www.vulncheck.com/advisories/barracuda-rmm-service-center-insecure-reflection-rce) for coordination details. Because exploitation is remote and unauthenticated once the Service Center is reachable, the most effective compensating control while patching is to restrict network access to the Service Center endpoint - close or ACL the SOAP/WSDL listener to trusted management hosts, partner IP ranges, and the vendor's own update infrastructure, placed behind VPN or a management jump host - with the trade-off that distributed technicians and integrations outside those allowlists will lose RMM connectivity until they are re-scoped. Network segmentation that isolates the Service Center from managed agents and general corporate/user networks reduces blast radius but does not eliminate the flaw, and blocking inbound WSDL import or SOAP service-registration functionality (where the deployment permits disabling it) removes the injection vector at the cost of any legitimate custom service integrations. Finally, log and alert on anomalous WSDL submissions and outbound SOAP calls from the Service Center host, since successful reflection/deserialization exploitation typically manifests as unexpected method invocations or child-process spawning by the service account.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerable component is Barracuda RMM's Service Center, the central web-services layer of the Remote Monitoring and Management platform, which consumes WSDL (Web Services Description Language) documents to define and invoke SOAP services. CWE-470 (Use of Externally-Controlled Input to Select Classes or Code, i.e. unsafe reflection) is the root-cause class: the application takes an attacker-controlled WSDL service name and uses it, without correct verification, to dynamically resolve and load classes or invoke methods, reflecting untrusted input directly into code-selection logic. Because the same input path is later processed by a deserializer, an attacker can also substitute untrusted types and trigger gadget-chain deserialization, giving two distinct RCE primitives (arbitrary method invocation or unsafe deserialization). The CPE cpe:2.3:a:barracuda:rmm:*:*:*:*:*:*:*:* confirms every pre-2025.1.1 release of the RMM product line is in scope; the flaw sits in the WSDL-handling/reflection boundary of the Service Center rather than in an authentication or transport layer, which is why the AV:N/AC:L/PR:N/UI:N vector permits unauthenticated exploitation with no user interaction once the endpoint is reachable.

Know when Barracuda gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 10.0 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
vuln.today AI 10.0 CRITICAL

Remote unauthenticated low-complexity RCE (AV:N/AC:L/PR:N/UI:N); S:C because RCE on the RMM platform compromises downstream managed systems beyond the vulnerable component, with full C/I/A impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Barracuda RMM's Service Center component (versions prior to 2025.1.1) contains a maximum-severity, unauthenticated remote code execution flaw that could allow an attacker to take control of the central management server. Because that server often orchestrates downstream managed endpoints, a compromise could cascade into customer environments and disrupt service delivery. Leadership should treat this as a high-priority exposure, while noting that no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include network isolation/VPN allowlisting for the Service Center endpoint, removing internet exposure, monitoring for malicious WSDL/deserialization activity, enforcing MFA and least privilege, and segmenting the RMM management plane from downstream managed systems.

Threat Intelligence Overview

EPSS Score
0.7%
Top 48% exploitable
Prevalence
Medium
MSP-focused RMM platform, common in managed-service environments but not universal
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.7%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)CVE.org

cpe:2.3:a:barracuda:rmm:*:*:*:*:*:*:*:*
CVE-2025-34392 CRITICAL POC
10.0 Dec 10

Unauthenticated remote code execution in the Barracuda RMM Service Center component (part of the RMM managed-service-pro

CVE-2017-6320 HIGH POC
8.8 Jul 18

A remote command injection vulnerability exists in the Barracuda Load Balancer product line (confirmed on v5.4.0.004 (20

CVE-2023-7102 CRITICAL POC
9.8 Dec 24

Use of a Third Party library produced a vulnerability in Barracuda Networks Inc. Rated critical severity (CVSS 9.8), thi

CVE-2023-2868 CRITICAL POC
9.8 May 24

A remote command injection vulnerability exists in the Barracuda Email Security Gateway (appliance form factor only) pro

CVE-2019-6724 HIGH POC
7.8 Mar 21

The barracudavpn component of the Barracuda VPN Client prior to version 5.0.2.7 for Linux, macOS, and OpenBSD runs as a

CVE-2023-26213 HIGH POC
7.2 Mar 03

On Barracuda CloudGen WAN Private Edge Gateway devices before 8 webui-sdwan-1089-8.3.1-174141891, an OS command injectio

CVE-2025-34394 CRITICAL
10.0 Dec 10

Unauthenticated remote code execution affects the Barracuda Service Center component of Barracuda RMM in all versions pr

CVE-2018-20369 MEDIUM POC
6.1 Dec 23

Barracuda Message Archiver 2018 has XSS in the error_msg exception-handling value for the ldap_user parameter to the cgi

CVE-2014-8428 CRITICAL
9.8 Aug 28

Privilege escalation vulnerability in Barracuda Load Balancer 5.0.0.015 via the use of an improperly protected SSH key.

CVE-2014-8426 CRITICAL
9.8 Aug 28

Hard coded weak credentials in Barracuda Load Balancer 5.0.0.015. Rated critical severity (CVSS 9.8), this vulnerability

CVE-2025-34395 HIGH
8.7 Dec 10

Unauthenticated remote attackers can read arbitrary files from Barracuda RMM versions prior to 2025.1.1 by invoking a pa

CVE-2021-42711 HIGH
7.8 Dec 01

Barracuda Network Access Client before 5.2.2 creates a Temporary File in a Directory with Insecure Permissions. Rated hi

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy