dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2026-21668

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 12.3.2.4465 or later.
See remediation →
71/100
Remediation priority · Elevated
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 bypass restrictions and manipulate arbitrary files on a Backup Repository.

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

This is an authorization bypass vulnerability in backup repository systems where an authenticated domain user can circumvent access controls to read, write, or manipulate arbitrary files on the backup repository. The CVSS 6.5 indicates network-exploitable with low privileges required, suggesting the attacker only needs standard domain credentials but can access files outside their intended scope.

MitigationApply vendor-provided patches immediately and review user permissions on backup repositories to ensure domain users only have access to files within their authorized scope until the patch is deployed.

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:>= 12.0.0.1402, < 12.3.2.4465

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
None
Integrity
High
Availability
None

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

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. Confirm Veeam Backup & Replication is installed
    Check for Veeam Backup & Replication installation by looking in Windows Programs and Features, or check for the Veeam installation directory (typically C:\Program Files\Veeam\Backup and Replication)
    Affected if Veeam Backup & Replication software is present on the system
  2. Identify installed version
    Open Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\, or run "Get-ItemProperty 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication'" in PowerShell to read the Version value
    Affected if The installed version falls within the range 12.0.0.1402 to 12.3.2.4465 (including 12.0.0.1402 and excluding 12.3.2.4465)
  3. Verify backup repositories are configured
    Open Veeam Backup & Replication console, navigate to Backup Infrastructure > Backup Repositories, or run Get-VBRBackupRepository in Veeam PowerShell to list configured repositories
    Affected if One or more backup repositories are configured and accessible to authenticated domain users
  4. Review repository access permissions
    In Veeam console, right-click each repository and select Properties > Access, or check the share permissions on the repository folder to see which domain users or groups have access
    Affected if Domain users or groups have access to backup repositories and can potentially bypass intended access controls

A system is affected if Veeam Backup & Replication version 12.0.0.1402 or higher but lower than 12.3.2.4465 is installed AND backup repositories are configured with domain user access.

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

Apply vendor-provided patches immediately and review user permissions on backup repositories to ensure domain users only have access to files within their authorized scope until the patch is deployed.

Recommended fix High confidence

Veeam Backup & Replication 12.3.2.4465 or later

  1. 1. Verify current Veeam Backup & Replication version by opening Veeam Backup & Replication console and checking Help > About, or using PowerShell Get-VBRServerInfo
  2. 2. Review Veeam Backup & Replication 12.3.2 release notes for any breaking changes or migration requirements relevant to your environment
  3. 3. Create a configuration backup of the current Veeam installation: open Veeam Backup & Replication, go to Configuration Backup, and create a manual backup
  4. 4. Schedule a maintenance window for the upgrade, ensuring backup jobs are not running
  5. 5. Download Veeam Backup & Replication version 12.3.2.4465 or later from the Veeam Customer Portal (www.veeam.com)
  6. 6. Run the installer on the Veeam server and follow the upgrade wizard prompts
  7. 7. After upgrade completes, verify the new version by checking Help > About shows version 12.3.2.4465 or later
  8. 8. Test that backup jobs, repository access, and authorization controls are functioning correctly
Caveat Review 12.3.x release notes for potential breaking changes; major version upgrades may require configuration adjustments or license reactivation

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

Fix this in Veeam Backup \& Replication Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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