Skip to main content
Mallory
CriticalVulnerability

CVE-2026-32998: Remote Code Execution in Veeam Service Provider Console Alarm Scripts

Published May 28, 2026 · Updated 23 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.4Critical · v4
EPSS0.52%45th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-32998CWE-233 · Improper Handling of Parameters

CVE-2026-32998 is a remote code execution vulnerability involving unsafe script execution parameters in the automated alarm system of Veeam Service Provider Console. A low-privileged remote attacker can exploit the vulnerable script execution functionality without user interaction. Affected releases include version 8 and version 9 builds through 9.2.0.33215. On version 9.2.0.33215, exposure depends on alarm script execution being enabled. The vulnerability is rated critical with a reported CVSS v3.1 score of 9.4 and is fixed in version 9.2.1.33875.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits remote code execution on the affected Veeam Service Provider Console system, compromising the confidentiality, integrity, and availability of the management environment. The supplied CVSS v4.0 vector also indicates high confidentiality, integrity, and availability impacts to subsequent systems, although specific downstream exploitation mechanisms are not established.

Mitigation

If you can’t patch tonight, do this now.

On version 9.2.0.33215, inspect the service configuration overrides JSON and set AlarmManagement_ScriptExecutionEnabled to false if it is true, then restart the Veeam Management Portal Service. If the setting is absent or already false, alarm script execution is disabled and the deployment is not affected by this vulnerability. Alarm script execution is disabled by default for new deployments and upgrades without previously configured alarm script actions. Earlier builds lack this setting and require an upgrade.

Remediation

Patch, then assume compromise.

Upgrade affected Veeam Service Provider Console deployments to version 9.2.1.33875 or later. Earlier releases, including versions 9.1, 9.0, and 8, do not support the documented alarm-script configuration workaround and must be upgraded.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-32998 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2026-32998 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-32998?
As of Oct 25, 2026, Mallory has found no public exploit for CVE-2026-32998.
Is there a patch for CVE-2026-32998?
Upgrade affected Veeam Service Provider Console deployments to version 9.2.1.33875 or later. Earlier releases, including versions 9.1, 9.0, and 8, do not support the documented alarm-script configuration workaround and must be upgraded.
How severe is CVE-2026-32998?
CVE-2026-32998 has a CVSS v4 score of 9.4 (Critical) and an EPSS score of 0.52% (45th percentile) as of Oct 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.