dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2022-26504

HIGH · 8.8 CVSS v3.1 Published 2022-03-17
Fix available
A fix is available. Upgrade to 10.0.1.4854 / 11.0.1.1261 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper authentication in Veeam Backup & Replication 9.5U3, 9.5U4,10.x and 11.x component used for Microsoft System Center Virtual Machine Manager (SCVMM) allows attackers execute arbitrary code via Veeam.Backup.PSManager.exe

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper authentication vulnerability in Veeam Backup & Replication's SCVMM integration component (Veeam.Backup.PSManager.exe) allows remote attackers to bypass authentication and execute arbitrary code due to insufficient authentication checks in versions 9.5U3, 9.5U4, 10.x, and 11.x.

MitigationApply the vendor-supplied patch or upgrade to a patched version of Veeam Backup & Replication to remediate the improper authentication flaw in the SCVMM component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Veeam Backup \& ReplicationApplication
Affected:>= 10.0.0.4442, < 10.0.1.4854>= 11.0.0.825, < 11.0.1.1261= 9.5.0.1536= 9.5.4.2615= 10.0.1.4854= 11.0.1.1261

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Veeam Backup & Replication is installed
    Look for Veeam installation directory in Program Files (typically C:\Program Files\Veeam\Backup and Replication\) or check Windows Registry under HKLM\SOFTWARE\Veeam\Veeam Backup & Replication
    Affected if The product is not installed or the registry keys do not exist, then this CVE does not apply.
  2. Identify installed Veeam Backup & Replication version
    Check the file version of Veeam.Backup.PSManager.exe in the installation directory, or read the installed version from the registry key HKLM\SOFTWARE\Veeam\Veeam Backup & Replication\Version
    Affected if The installed version falls within these affected ranges: 9.5.0.1536, 9.5.4.2615, 10.0.0.4442 through 10.0.1.4854 (inclusive), or 11.0.0.825 through 11.0.1.1261 (inclusive).
  3. Confirm SCVMM integration component is present
    Verify that the file Veeam.Backup.PSManager.exe exists in the Veeam installation directory (such as in the Backup and Replication\Veeam.Backup.PSManager folder)
    Affected if The component file exists - if the component is present and the version is in the affected ranges listed above, the system is vulnerable.
  4. Check if SCVMM integration is configured or enabled
    Review Veeam backup infrastructure settings within the Veeam Backup & Replication console for any configured Microsoft System Center Virtual Machine Manager (SCVMM) integration points
    Affected if SCVMM integration is configured or the component is actively used - exploitation requires the SCVMM integration to be accessible to remote attackers.

You are affected if Veeam Backup & Replication is installed with a version matching 9.5.0.1536, 9.5.4.2615, 10.0.0.4442 through 10.0.1.4854, or 11.0.0.825 through 11.0.1.1261 AND the SCVMM integration component (Veeam.Backup.PSManager.exe) is present and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.1.4854 / 11.0.1.1261 or later
Fixed in 10.0.1.485411.0.1.1261
Interim mitigation

Apply the vendor-supplied patch or upgrade to a patched version of Veeam Backup & Replication to remediate the improper authentication flaw in the SCVMM component.

Recommended fix Moderate confidence

Veeam Backup & Replication 10.0.1.4854 or 11.0.1.1261 (or later stable release)

  1. 1. Back up your current Veeam Backup & Replication configuration and data.
  2. 2. Review the Veeam Backup & Replication Release Notes for version 10.0.1.4854 or 11.0.1.1261 for compatibility and known issues.
  3. 3. Download the fixed version from the Veeam Customer Portal (veeam.com).
  4. 4. Run the Veeam Backup & Replication installer and follow the upgrade wizard.
  5. 5. After upgrade, verify the Veeam.Backup.PSManager.exe component is properly updated and functional.
  6. 6. Test SCVMM integration to confirm the fix works correctly.
Caveat Review release notes for any breaking changes between your current version and the target version; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Veeam Backup \& Replication Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26504 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data