dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2026-21669

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 13.0.1.2067 or later.
See remediation →
100/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
A vulnerability allowing an authenticated domain user to perform remote code execution (RCE) on the Backup Server.

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

An authenticated domain user can achieve remote code execution on a Backup Server, likely due to insufficient authorization checks or improper input validation in the Backup Server component, allowing arbitrary command execution with elevated privileges.

MitigationIsolate Backup Server network segments, enforce least-privilege access controls, implement additional authentication layers, and apply vendor patches once available. Consider disabling unnecessary services on the Backup Server until remediation.

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:>= 13.0.0.496, < 13.0.1.2067

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Check Veeam Backup & Replication version
    Open the Veeam Backup & Replication console, go to Help > About, or run 'Get-VBRServerInfo' in PowerShell to view the installed version number.
    Affected if The version is 13.0.0.496 or higher, but lower than 13.0.1.2067.
  2. Confirm Backup Server component is configured
    In the Veeam console, navigate to Inventory > Backup Servers to verify the Backup Server is added and active in the environment.
    Affected if A Backup Server is present and operational in the Veeam infrastructure.
  3. Review domain user authentication settings
    Check the Veeam console under Users and Roles or examine local/group policy settings for domain user permissions to the Backup Server component.
    Affected if Domain users have been granted access to manage or interact with the Backup Server.
  4. Verify elevated privilege assignments
    Inspect the permissions assigned to domain users or groups in Veeam under Administration > Users and Roles to see if any domain accounts have administrative or elevated privileges.
    Affected if Domain users have been assigned administrative or elevated roles within Veeam.

A user is affected if they have Veeam Backup & Replication version 13.0.0.496 or higher but below 13.0.1.2067, with the Backup Server component configured and domain users granted access to it.

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 13.0.1.2067 or later
Fixed in 13.0.1.2067
Interim mitigation

Isolate Backup Server network segments, enforce least-privilege access controls, implement additional authentication layers, and apply vendor patches once available. Consider disabling unnecessary services on the Backup Server until remediation.

Recommended fix Moderate confidence

Veeam Backup & Replication 13.0.1.2067 or later

  1. 1. Verify current Veeam Backup & Replication version by opening the Veeam Backup & Replication console and navigating to Help > About, or run 'Get-VBRServerInfo' in PowerShell
  2. 2. If version is >= 13.0.0.496 and < 13.0.1.2067, plan for upgrade during a maintenance window
  3. 3. Create a full backup of the Veeam configuration using the console (Backup & Replication > Jobs > Configuration Backup) or command line 'veeamconfig config backup'
  4. 4. Download Veeam Backup & Replication version 13.0.1.2067 or later from the Veeam downloads portal (www.veeam.com/downloads.html)
  5. 5. Run the installer with administrator privileges on the Veeam Backup server
  6. 6. Follow the upgrade wizard prompts, ensuring the 'Upgrade' option is selected
  7. 7. After upgrade completes, verify the new version by checking Help > About
  8. 8. Test critical backup and restore operations to confirm functionality
Caveat Review Veeam Release Notes for version 13.0.1 for any configuration or feature changes that may require adjustment

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

Fix this in Veeam Backup \& Replication Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21669 — 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-2026-21669 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