Holes in Veeam Backup suite allow remote code execution, creation of malicious backup config files
The vendor has issued a patch to close four holes in its flagship Backup & Replication suite; version 13 users are advised to audit their backup config files and closely monitor backup jobs.
Veeam says that four vulnerabilities could allow a person with certain oversight roles for its flagship Backup & Replication suite to do serious damage to – but not destroy – a backup database.
The company has already issued a patch for the bugs, which, it says, should be applied immediately.
The worst of the vulnerabilities, CVE-2025-59470, carries a criticality score of 9 and would allow a threat actor “to do something nefarious,” said , Veeam’s vice-president of product strategy.
But he emphasized that, because of the immutable nature of the backup, data can’t be destroyed.
The issue: Veeam discovered that a person with the role of Backup Admin, Backup Operator, or Tape Operator status in unpatched version 13 of the suite (versions 13.0.1.180 and earlier) have more permissions than they should. The patch corrects that.
- CVE-2025-59470 (with a CVSS score of 9) allows a Backup or Tape Operator to perform remote code execution (RCE) as the Postgres user by sending a malicious interval or order parameter;
- CVE-2025-59469 (with a severity score of 7.2) allows a Backup or Tape Operator to write files as root;
- CVE-2025-55125 (with a severity score of 7.2) allows a Backup or Tape Operator to perform remote code execution (RCE) as root by creating a malicious backup configuration file;
- CVE-2025-59468 (with a severity score of 6.7) allows a Backup Administrator to perform remote code execution (RCE) as the Postgres user by sending a malicious password parameter.
The patch to version 13.0.1.1071 will be an “easy installation” that won’t be disruptive, Vanover said. As of Tuesday afternoon, Veeam hadn’t received reports of exploitation, he adde



