Vulnerability Resolved in Veeam Service Provider Console 9.2.1

KB ID: 4853
Product: Veeam Service Provider Console | 9 | 9.1 | 9.2
Published: 2026-05-27
Last Modified: 2026-05-27
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

All vulnerabilities documented in this article were resolved in Veeam Service Provider Console 9.2.1.33875.
Veeam Software Security Commitment
Veeam® is committed to ensuring its products protect customers from potential risks. As part of that commitment, we operate a Vulnerability Disclosure Program (VDP) for all Veeam products and perform extensive internal code audits. When a vulnerability is identified, our team promptly develops a patch to address and mitigate the risk. In line with our dedication to transparency, we publicly disclose the vulnerability and provide detailed mitigation information. This approach ensures that all potentially affected customers can quickly implement the necessary measures to safeguard their systems. It’s important to note that once a vulnerability and its associated patch are disclosed, attackers will likely attempt to reverse-engineer the patch to exploit unpatched deployments of Veeam software. This reality underscores the critical importance of ensuring that all customers use the latest versions of our software and install all updates and patches without delay.

Issue Details

All vulnerabilities disclosed in this article affect Veeam Service Provider Console 9.2.0.33215 and all earlier version 9 builds.

CVE-2026-32998

A vulnerability in Veeam Service Provider Console allows for remote code execution.

Severity: Critical
CVSS v3.1 Score: 9.4CVSS:AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Source: Reported by putsi through HackerOne.

Solution

This vulnerability was fixed starting with the following build:

Mitigation

This vulnerability is related to script execution within alarms, which is disabled by default in v9.2 unless the VSPC instance already has alarms configured with a script execution action. If no such alarms exist, the vulnerability is not applicable.

To check whether an instance is affected:

  1. On the Veeam Service Provider Console server, open the following file in a text editor:
    C:\ProgramData\Veeam\Veeam Availability Console\Configuration\Service\configuration.overrides.json
    
  2. Within the configuration.overrides.json file, review the value of:
    "AlarmManagement_ScriptExecutionEnabled"
    
    • If this value is set to False, then the deployment is not affected.
    • If the value is set to True, the issue can be mitigated prior to applying v9.2.1, by setting the value to "False" and restarting the Veeam Management Portal Service.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.