dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2026-21667

HIGH · 8.8 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 12.3.2.4465 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
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. The specific attack vector (e.g., command injection, deserialization flaw, insecure deserialization) is not detailed, but the high CVSS indicates a severe code execution flaw exploitable by users with standard domain credentials.

MitigationApply vendor-provided security patches immediately; until then, restrict domain user access to the backup server segment and monitor for unusual activity.

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
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. Identify Veeam Backup & Replication installation
    Locate Veeam Backup & Replication installed on the system. Common installation paths include C:\Program Files\Veeam\Backup and Replication\ or check Programs and Features in Control Panel for 'Veeam Backup & Replication'.
    Affected if Veeam Backup & Replication is installed on the system
  2. Determine installed version number
    Open the Veeam Backup & Replication console, go to Help > About, or check the installed programs list. The version is displayed in the format such as 12.x.x.xxxx.
    Affected if A version number is displayed in the console or installed programs list
  3. Compare version against affected range
    Compare your installed version to the vulnerable range: 12.0.0.1402 (inclusive) through 12.3.2.4464 (exclusive). Versions 12.0.0.1402 up to but not including 12.3.2.4465 are affected.
    Affected if Installed version is greater than or equal to 12.0.0.1402 AND less than 12.3.2.4465
  4. Confirm role is Backup Server
    In the Veeam console, verify this installation is configured as a Backup Server role (not just a proxy or repository). Check the server properties or infrastructure view.
    Affected if This system is configured as a Backup Server and version falls within the affected range

If Veeam Backup & Replication is installed as a Backup Server with a version between 12.0.0.1402 and 12.3.2.4464, the environment is affected by this authenticated RCE vulnerability.

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 security patches immediately; until then, restrict domain user access to the backup server segment and monitor for unusual activity.

Recommended fix High confidence

12.3.2.4465 or later

  1. Check current Veeam Backup & Replication version via the console (Help > About) or PowerShell (Get-VBRServerInfo)
  2. Download the updated version (12.3.2.4465 or later) from the official Veeam downloads page (www.veeam.com)
  3. Create a configuration backup before upgrading (in the console: Menu > Backup Infrastructure > Configuration Backup > Backup Now)
  4. Run the installer/upgrade package on the backup server
  5. Follow the on-screen wizard prompts to complete the upgrade
  6. After upgrade, verify all services are running and the version has been updated
  7. Confirm the vulnerability is resolved by checking the version is now >= 12.3.2.4465
Caveat Review Veeam release notes for version 12.3.x 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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