dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2025-59470

CRITICAL · 9.0 CVSS v3.1 Published 2026-01-08
Fix available
A fix is available. Upgrade to 13.0.1.1071 or later.
See remediation →
96/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
This vulnerability allows a Backup Operator to perform remote code execution (RCE) as the postgres user by sending a malicious interval or order parameter.

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 vulnerability allows a Backup Operator to achieve remote code execution as the postgres user by sending malicious interval or order parameters, likely due to improper input validation or command injection in the backup functionality.

MitigationImplement strict input validation and sanitization on interval and order parameters, and run the backup functionality with least-privilege principles to limit the postgres user permissions.

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.4967, < 13.0.1.1071

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/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 Veeam Backup & Replication version
    Open the Veeam Backup & Replication console, go to Help > About, or run: Get-VBRServer | Select-Object Version. Alternatively, check the Windows Registry at HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\Version
    Affected if The installed version is greater than or equal to 13.0.0.4967 AND less than 13.0.1.1071
  2. Verify backup jobs exist
    In the Veeam console, navigate to Home > Backup Jobs, or run: Get-VBRBackupJob to list configured backup jobs
    Affected if Any backup, replica, or backup copy jobs are configured and enabled, as the vulnerability resides in the backup functionality parameters
  3. Confirm Backup Operator accounts
    In Veeam, go to Users and Roles > Roles, or check AD security groups assigned the Backup Operator role. Run: Get-VBRRole to list roles and their members
    Affected if Any user or security group is assigned the Backup Operator role and can access the backup infrastructure
  4. Check for vulnerable parameter exposure
    Review any exposed backup API endpoints or scripts that accept interval or order parameters for backup operations. Inspect any custom scripts or integrations using the Veeam PowerShell SDK that invoke backup job settings with these parameters
    Affected if Custom scripts, API calls, or integrations pass interval or order parameters to backup job functions without input validation

You are affected if Veeam Backup & Replication version is 13.0.0.4967 through 13.0.1.1070 and backup jobs or the Backup Operator role are in use, allowing an operator to send malicious interval or order parameters to the backup functionality.

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.1071 or later
Fixed in 13.0.1.1071
Interim mitigation

Implement strict input validation and sanitization on interval and order parameters, and run the backup functionality with least-privilege principles to limit the postgres user permissions.

Recommended fix Moderate confidence

Veeam Backup & Replication 13.0.1.1071 or later

  1. Verify current Veeam Backup & Replication version by checking the About section in the console or using the Veeam Backup & Replication console
  2. Download Veeam Backup & Replication version 13.0.1.1071 or later from the official Veeam website (www.veeam.com)
  3. Review Veeam upgrade documentation and ensure all prerequisites are met before upgrading
  4. Create a full backup of the Veeam configuration database before proceeding with the upgrade
  5. Execute the upgrade installer on the Veeam Backup & Replication server
  6. Follow the on-screen upgrade wizard prompts to complete the installation
  7. After upgrade, verify the version shows 13.0.1.1071 or later in the About section
  8. Test that backup jobs and related functionality operate normally after the upgrade
Caveat Standard Veeam upgrade - review release notes for any configuration or feature changes between versions

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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