dbcve.org
Veeam Backup \& ReplicationApplication · Veeam

CVE-2025-55125

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-08
Fix available
A fix is available. Upgrade to 13.0.1.1071 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 or Tape Operator to perform remote code execution (RCE) as root by creating a malicious backup configuration file.

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 users with Backup or Tape Operator privileges to achieve root-level remote code execution by crafting a malicious backup configuration file. The issue appears to stem from improper validation or insecure handling of backup configuration files that are processed with elevated privileges, enabling privilege escalation from a relatively low-privilege account to root.

MitigationRestrict Backup and Tape Operator role assignments to trusted personnel only, and implement strict validation of backup configuration files before processing. Apply vendor patches immediately when 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:>= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Veeam Backup & Replication version
    Open Veeam Backup & Replication console, go to Help > About, or run 'veeamversion' command in PowerShell. Locate the exact build number displayed.
    Affected if The version is 13.0.0.4967 or higher, but lower than 13.0.1.1071
  2. Confirm the product is Veeam Backup & Replication
    Verify the installed product is Veeam Backup & Replication (not Veeam ONE or other Veeam products) from the About window or installed programs list.
    Affected if The product is Veeam Backup & Replication version 13.0.0.4967 through 13.0.1.1070
  3. Review Backup Operator role assignments
    Open Veeam Backup & Replication console, navigate to Users and Roles > Roles. Check which users or groups are assigned the Backup Operator role.
    Affected if Any user account has Backup Operator role and the version is vulnerable
  4. Review Tape Operator role assignments
    In the same Users and Roles section, verify if any users or groups are assigned the Tape Operator role.
    Affected if Any user account has Tape Operator role and the version is vulnerable
  5. Check for accessible backup configuration file processing
    Verify that users with Backup or Tape Operator roles can import or create backup configuration files. Check if the backup configuration import/creation interface is accessible to these roles.
    Affected if Backup or Tape Operator users can import or create backup configuration files in the Veeam environment

A user is affected if Veeam Backup & Replication version is between 13.0.0.4967 and 13.0.1.1070 inclusive, and any user holds Backup Operator or Tape Operator role with ability to process backup configuration files.

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

Restrict Backup and Tape Operator role assignments to trusted personnel only, and implement strict validation of backup configuration files before processing. Apply vendor patches immediately when available.

Recommended fix High confidence

Veeam Backup & Replication 13.0.1.1071 or later

  1. Verify current Veeam Backup & Replication version by checking About section in the console
  2. Download Veeam Backup & Replication version 13.0.1.1071 or later from the official Veeam download portal (www.veeam.com)
  3. Review Veeam Backup & Replication 13.0.1 release notes for any known issues or prerequisites
  4. Create a full backup of the Veeam configuration database before upgrading
  5. Stop all Veeam services on the backup server (or use the setup wizard to upgrade with services automatically stopped)
  6. Run the Veeam Backup & Replication installer with administrator privileges
  7. Follow the upgrade wizard prompts, selecting 'Upgrade' when prompted
  8. Allow the installer to restart Veeam services automatically
Caveat Review Veeam 13.0.1 release notes for any configuration or feature changes that may require adjustment; test in staging environment before production deployment

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-2025-55125 — 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-55125 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