dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2026-21708

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 12.3.2.4465. 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 a Backup Viewer to perform remote code execution (RCE) as the postgres user.

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

A critical remote code execution vulnerability exists in a Backup Viewer component that allows an authenticated Backup Viewer to execute arbitrary code as the postgres user. This suggests the Backup Viewer lacks proper access controls or input validation, potentially allowing command injection or improper privilege escalation within the PostgreSQL database environment.

MitigationImmediately restrict access to the Backup Viewer to only authorized personnel, implement network segmentation to limit exposure, and apply any available vendor patches. If no patch exists, consider disabling the Backup Viewer component until a fix is available.

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

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

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 installed Veeam Backup & Replication version
    Open Veeam Backup & Replication console, go to Help > About, or run 'veeamversion' command from the installation directory to obtain the exact build number
    Affected if The displayed version is 12.0.0.1402 or higher but lower than 12.3.2.4465
  2. Verify Backup Viewer component is accessible
    Attempt to access the Backup Viewer web interface at port 9105 (default) or check if the BackupViewerService is running on the Veeam server
    Affected if The Backup Viewer service is running and the web interface is accessible on the network
  3. Identify configured Backup Viewer users
    In Veeam console, go to Users and Roles > Roles, or check the SQL database (VeeamBackupReporting) for users assigned the Backup Viewer role
    Affected if There are one or more user accounts assigned the Backup Viewer role in the Veeam deployment
  4. Confirm postgres user context availability
    Check if the Veeam database connection uses a postgres service account, by reviewing connection strings in Veeam configuration files (typically in C:\Program Files\Veeam\Backup and Replication\Configuration\DbSettings.xml) or in SQL Server logs
    Affected if The Veeam Backup & Replication database is running on PostgreSQL and uses the postgres service account for database connections

A system is affected if it runs Veeam Backup & Replication version 12.0.0.1402 through 12.3.2.4464, has the Backup Viewer component enabled, and has Backup Viewer users configured with a PostgreSQL database backend.

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

Immediately restrict access to the Backup Viewer to only authorized personnel, implement network segmentation to limit exposure, and apply any available vendor patches. If no patch exists, consider disabling the Backup Viewer component until a fix is available.

Recommended fix Moderate confidence

Veeam Backup & Replication 12.3.2.4465 or later

  1. 1. Verify current Veeam Backup & Replication version by checking the About section in the Veeam console or using the command line: Get-VBRVersion
  2. 2. If version is >= 12.0.0.1402 and < 12.3.2.4465, plan for upgrade during a maintenance window
  3. 3. Before upgrading, create a complete backup of the Veeam configuration database and verify all backups are working
  4. 4. Download Veeam Backup & Replication version 12.3.2.4465 or later from the official Veeam download portal (www.veeam.com)
  5. 5. Review Veeam Upgrade Guide for version 12.3.x to ensure all prerequisites are met
  6. 6. Execute the upgrade installer with appropriate permissions (typically requires local administrator and SQL sysadmin rights)
  7. 7. After upgrade, verify the Veeam services start correctly and the console is accessible
  8. 8. Confirm the vulnerability is remediated by verifying the version shows 12.3.2.4465 or later
Caveat Review Veeam 12.3 release notes for any configuration or feature changes before upgrading; 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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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