CVE-2025-34393: Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not correctl

Q: How do I fix CVE-2025-34393?

rmm: upgrade to 2025.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-34393 being exploited?

CVE-2025-34393 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-34393 affect?

CVE-2025-34393 affects rmm. Severity is critical (CVSS 9.8). 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

Q: How urgent is CVE-2025-34393?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2025-34393 is a critical-severity flaw (CVSS 9.8) affecting rmm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-470
Published	2025-12-10
Last modified	2026-10-14

Publisher (CNA): VulnCheck · Vendor: barracuda

Last updated 2026-10-14 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-12-10 16:16 UTCPublished CVE record published
2026-10-14 21:10 UTCUpdated Record last modified

barracuda rmm UPGRADE

Affected: < 2025.1.1

Fixed in: 2025.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy rmm || rpm -q rmm || rmm --version

2. UPGRADE to 2025.1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade rmm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade rmm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-34393?

rmm: upgrade to 2025.1.1. Exact commands for each OS are on this page.

Is CVE-2025-34393 being exploited?

CVE-2025-34393 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-34393 affect?

CVE-2025-34393 affects rmm. Severity is critical (CVSS 9.8). 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

How urgent is CVE-2025-34393?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-34392 CRITICAL 9.8 UPGRADE Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not verify t
CVE-2025-34394 CRITICAL 9.8 UPGRADE Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, exposes a .NET Re
CVE-2025-34395 HIGH 7.5 UPGRADE Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, exposes a .NET Re

References

← Back to latest CVEs